Bug#311774: lprng: Fails to print to localhost when named pipe is missing
>>>>> "CS" == Craig Small <firstname.lastname@example.org> writes:
CS> On Tue, Mar 14, 2006 at 10:22:21AM +0100, Anders Boström wrote:
>> >>>>> "CS" == Craig Small <email@example.com> writes:
CS> On Mon, Mar 13, 2006 at 09:55:51AM +0100, Anders Boström wrote:
>> >> I'm not quite sure what you mean... I've never used the
>> >> force_localhost directive, and if I turn it on, direct printing is
>> >> turned on, but I don't want that, I want to use the local
>> >> spool. Without force_localhost, I just get this:
CS> It is turned on. So that means it is trying to get to the socket
CS> which means it gives errors like:
>> >> Printer 'sda4_local@localhost' - cannot open connection - No such file or directory
>> >> Make sure the remote host supports the LPD protocol
CS> The problem is your printcap shows all these things that make sense
CS> outside the chroot but do not make sense inside it. Unless you tell it
CS> otherwise, it will attempt to contact the daemon through the socket.
>> Yes, that's what this report is all about! How do I avoid usage of the
>> local socket??? How do I "tell it otherwise"???
CS> It's called turning off force_localhost.
No :force_localhost@ don't work! It don't give the desired effect. It
prints directly, without using the local spool. I want to print via
Turning off force_localhost is not the solution to this problem!
>> At least document the current (miss)behavior, and suggest a
>> work-around! Mount bind of /var/run is the best I've come up with.
CS> It's in both the README and the HOWTO.
Can you please specify the files you suggest that I read!
/usr/share/doc/lprng/README.Debian don't have any information about
printing from a chroot via a local spool. Neither do
/usr/share/doc/lprng-doc/README.gz . And I can't find this in