Bug#199094: lprng: Doesn't want to have lpd running all the time

[Tomasz Chmielewski <mangoo@wpkg.org>]

Is lprng still developed at all?

Here is the answer to Craig's question on lprng mailing list:


One of the problems  that other severs do not have to deal with is
restarting operations.  The print spooler is considered broken
if, after rebooting, printing of jobs in the spool queue are not
automatically started.

After several years and (literally) hundreds of queiries about this
I ripped out the inetd support in the old PLP software.

Having said this,  if you want to add it, do the folllwing:

a) /etc/lpd.conf - set unix_socket_path to 'no' or '' to
   suppress the use of the Unix socket (/var/run/lpd)

b) add a '-i' option oto lpd.c that will cause:
    fd 1, 2 to be opened to /dev/null
    dup fd 0 to Listen_FD
    close fd 0 and dup fd 1 to fd 0
    skip the socket/bind/listen for the TCP/IP lpd listen
    socket.

    Remove the lpd startup code from wherever it is hiding.
    Add entry to /etc/inetd  with 'wait' for the mode, and -i option.

    killall lpd
    killall -HUP inetd   (or killal -pHUP xinetd)

    Test. Rinse. Repeat. Reboot. Test. Rinse... etc.


Good luck.  If you do this,  perhaps you can post patches
and some documentation.  Then if other folks want to do
this,  we can have some information for them.



Tomasz Chmielewski
http://wpkg.org