reopen 319381 stop >>>>> "DBTS" == Debian Bug Tracking System <[EMAIL PROTECTED]> writes:
DBTS> Anders asked: >> What option should I use in lpd.conf? >> >> I don't want to connect directly to a remote printer. I want to >> connect to the local lpd-server, but not by using >> /var/run/lprng/socket (as it is absent in the chroot), so >> force_localhost don't work. DBTS> lpd.conf in examples has: DBTS> # Purpose: path for UNIX socket for localhost connections DBTS> # default unix_socket_path= /var/run/lprng/socket (STRING) This still don't solve the main problem, as /var/run/lprng/socket isn't available in the chroot. As I see it, there are two ways to solve this problem: 1. Make lpr fall back to using the network socket when the local socket isn't available. 2. Or document that in order to print from a chroot is /var/run/lprng/socket needed in the chroot and suggest the following line in the fstab: /var/run /your-chroot/var/run none bind 0 0 Also, the current error message: "Printer '[EMAIL PROTECTED]' - cannot open connection - No such file or directory Make sure the remote host supports the LPD protocol and accepts connections from this host and from non-privileged (>1023) ports" is miss-leading. If the error message was in line with "Error: can't connect to local socket /var/run/lprng/socket" would the problem be much easier to solve. Several people have reported problems (on mailing-lists) with printing from a chroot. It isn't obvious that you have to bind /var/run in the chroot, and I haven't found any documentation on this. At least document it! / Anders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
