>> After much coaxing, we discovered that the reason people could not
>> lprm their own jobs was that the connection-handling lpd was receiving
>> a SIGSEGV and exiting.
Mike made a slight mistake here (I'm the aforementioned coworker);
the stack trace is actually from an "lpc start" of a print queue. lprm
does not cause the child lpd to segv, but also fails to work, apparently
because of changed semantics in the lpd.perms file.
Garry Zacheiss
MIT Athena Server Operations
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
