Hi there,
Thanks for the reply.
> These processes are 'zombies' waiting for the main LPD process to
> harvest (wait) for them. The LPD code is waiting in a select
> loop for either a process to exit or for a connection.
>
> Setup_waitpid_break();
> errno = 0;
> fd_available = select( max_socks,
> FD_SET_FIX((fd_set *))&readfds,
> FD_SET_FIX((fd_set *))0,
> FD_SET_FIX((fd_set *))0, timeout );
> err = errno;
> Setup_waitpid();
>
> plp_signal_t sigchld_handler (int signo)
> {
> signal( SIGCHLD, SIG_DFL );
> write(Lpd_request,"\n", 1);
> }
>
> void Setup_waitpid (void)
> {
> signal( SIGCHLD, SIG_DFL );
> }
>
> void Setup_waitpid_break (void)
> {
> (void) plp_signal_break(SIGCHLD, sigchld_handler);
> }
>
> So under load, the LPD server will probably wait in the select for a
> while.
So, this is purely a load issue? Looks like I'll need to set up
another print server then.
As a side-issue, is there a way to stop a queue from accepting new
print jobs, while it clears away the backlog? I had always thought
that 'lpc disable' did this, but it stops anything after the current
job from printing.
Cheers
Toby
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
