lprng-devel Mailing List for LPRng

* walter harms <wh...@bf...> [120120 11:16]:
> hi list,
> i am using lprng in several boxes and now i have a problem that stunned me.
> I was chasing missing files and found the following hint: in ./log
>
> Wait_for_pid: LP filter died with signal 'Interrupt'

The string 'Interrupt' is from sys_siglist, which here (EGLIBC 2.11.2-10
on i386) has that value only for a value of '1' which is here SIGHUP.

SIGHUP is quite a strange signal to have caught by a filter, but it
looks like lprng is using it.

If you can reproduce it, you might want to enable debugging (especially DCTRL1
to be set with the 'lpc' debug keyword) in lprng to see if it says
anything about it.

Unless some signal is reaching the wrong recipient (lprng is often
sending itself (or forks of itself) a HUP), that should happen, if:

- the job is removed while the filter is still running (lpd_remove.c:299ff)
- the filter is run by one of the client programs (most likely lpr) and
  that received a HUP (perhaps because it is not finished before its
  controling terminal vanishes) and sent it to all of its children
  (via cleanup_HUP).

	Bernhard R. Link

hi list,
i am using lprng in several boxes and now i have a problem that stunned me.
I was chasing missing files and found the following hint: in ./log

Wait_for_pid: LP filter died with signal 'Interrupt'

it seems to happen only when a suddenly 20 or more files enter the queue.

my entry looks like that here:

insert:\
        :lp=|-$/usr/bin/insert -d0 :\
        :sd=/var/spool/lpd/insert:\
        :lf=/var/spool/lpd/insert/log:\
        :af=/var/spool/lpd/insert/acct:\
        :la@:\
        :tr=:cl:lk:sh:


To make things worse i tested /usr/bin/insert that has no problems handling the data files (even much more
does not make any difference).

any hints here ?

re,
 wh