--On March 13, 2008 8:16:42 AM -0400 Nathan Brindle <[log in to unmask]>
wrote:

> At 07:36 PM 3/12/2008 -0600, Ben Parker wrote:
>> On Wed, 12 Mar 2008 16:34:44 -0600, Michael Loftis <[log in to unmask]>
>> wrote:
>>
>>> I noticed that the new go script detects and (tries) to use
>>> lsv-logger.pl  if it's executable, however, I've had to turn it
>>> off/disable lsv-logger.pl  because it's causing listserv to spin and
>>> put thousands of lines of "Paused  - enter a command:" like lsv is
>>> still in normal foreground mode and  expecting input somehow.
>>>
>>> Anyone have any clues?
>>
>> The problem can be corrected in the 'go' script.   Change this line
>>
>>     lsvlog="2>&1 >>$LOG_PATH/listserv-`date +%Y%m%d`.log"
>
> Sorry, that's incorrect.  The correct line to change is
>
>            lsvlog="2>&1 | ./lsv-logger.pl $LOG_PATH"

Ah Thanks, I guess if i thought about it piping in /dev/null would be
obvious.  I just noticed when I quickly perused the go script it was
clearly looking for the lsv-logger.pl and using it if it existed.  Didn't
actually look any closer.  I knew what you meant though ;)

Thanks Nathan!



>
>
>> to this:
>>
>>     lsvlog="< /dev/null 2>&1 | ./lsv-logger.pl $LOG_PATH"
>>
>> This will be corrected in the next build or level set release.
>
> Nathan
>



--
"Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds."
-- Samuel Butler