It turns out that none of the file permissions in spool were changed
directly.  I was logged in running lcmd at the time.  I recall that I thought
it wasn't working properly, so I ran a backup copy of the binary.  The backup
copy, I didn't realize, was owned by root, not the listserv id.  I'm guessing
this caused the problem?  If so, I won't do that next time. :)

- Kathy M.

Kathy Montgomery wrote:

> Thanks:  I looked in spool and it happened exactly as you said:
>
> -rw-------   1 root     listserv       57 Mar  1 15:49 1365791.jobh
>
> The modification time of the file is when the crash happened.
>
> - Kathy M.
>
> Nathan Brindle wrote:
>
> > This suggests that someone changed the ownership or permissions on one
> > or more of the files in LISTSERV's spool directory, or possibly that
> > lsv_amin is no longer owned by 'listserv'.  Either way the error means
> > that LISTSERV does not have permission to open the job file in question.
> >
> > Nathan