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? -- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler