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"


>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