README for Debian package of LPRng ================================== This is a collection of things that you should read, especially if you are having troubles with LPRng or your printers. Please also note there is a LPRng-HOWTO in the lprng-doc package. Network Printer not Printing ---------------------------- #1 source of all my bug reports would have to be this. Someone has a networked printer (that is a printer with its own IP address), they've upgraded from some old LPRng, say 3.6.12 or lower, and now the printer stops working and the jobs just disappear. You probably have something in your /etc/printcap like lp=/dev/null as well as some rp and rm lines. Well, the job is going to the lp line and ending up in /dev/null, remove that line out of printcap. Or you might have a lpr_bounce clause in there which should be removed. Remote Users not being able to print ------------------------------------ From LPRng version 3.6.20-1 onwards you can stop people remotely accessing your lpd. Of course you sometimes do want remote users to access lpd or you want to do some funky things with /etc/lprng/lpd.perms then you can change it yourself. Of course if you have a pre 3.6.20-1 lpd.perms and you want to stop people from remotely connecting then add the following line to the top of /etc/lprng/lpd.perms REJECT NOT SERVER Remote Printers and no spool file --------------------------------- Some people want to directly print to their remote printers without having all the spooling etc on the Linux box. Some old versions allowed this to happen out of the box. The newer LPRngs do not because it is generall a bad idea. But if you want to do it, put something like this in your /etc/printcap lp1:rp=pr:rm=10.0.1.2 :force_localhost@ Also read the LPRng-HOWTO for more information. Why is GDBM disabled in configure? ---------------------------------- In 3.7.3 gdbm was introduced. Unfortunately it uses some definitions that I could not find (certainly, they won't in gdbm.h), so it was disabled. lpd does not start or you get connection refused messages --------------------------------------------------------- From version 3.8.2 there are two new reasons why LPRng's lpd server will not start. The first is that the /etc/printcap file is not installed by default as it is shared amongst many packages and the lprng package should not claim ownership over it. Look in /usr/share/doc/lprng/examples for an example printcap. Secondly there is a debconf question which asks if you want lpd to be started, most people should say yes. Debconf Translations -------------------- My thanks to the following translators: German: Michael Bramer Swedish: Andr? Dahlqvist French: Thomas Morin