Date:          Mon, 1 Feb 1999 20:38:08 -0500
From:          "Robert A. Earl" <[log in to unmask]>

Suddenly (no changes made that I know of) my ListServ-Lite Free Edition won't start!
The 'go' script thinks it's gonna, but nothing happens.  The log is empty.  I
emptied the spool dir, thinking that perhaps a bad job was killing it...any
suggestions?
-----------------------snip---------------------------------
Date:          Mon, 1 Feb 1999 20:38:08 -0500
From:          "Robert A. Earl" <[log in to unmask]>

Suddenly (no changes made that I know of) my ListServ-Lite Free Edition won't start!
The 'go' script thinks it's gonna, but nothing happens.  The log is empty.  I
emptied the spool dir, thinking that perhaps a bad job was killing it...any
suggestions?
Here is the output (except password) from 'sh -x go' :

--------------- snip -----------------

Robert,

you have probably already checked but I will suggest it anyway....

all files under listserv need to be owned by listserv itself.... often the log
file if created manually will not be owned by listserv and therefore will not
record any data....

looks like you have unix so try a:

ps -ef | grep lsv
(or equivalent in whatever system)

if you have at least one lsv process running then listserv is working and the
log file is not functioning for some reason.... generally permissions

if it is not running then you need to check out you aliasing for listserv.....
there should be 2 entries approximately like this:

listserv: "|/usr/local/bin/lsv_amin /home/listserv/spool listserv"
owner-listserv: "|/usr/local/bin/lsv_amin /home/listserv/spool owner-listserv"

with the appropriate absoute path names to the refered files.....

another common problem is the soft links if you have any that reference to the
location for listserv and any of its associated directories...

hope this helps....

Debra
carpe diem.... carpe jugulum