On Thu, 23 Dec 1999, Michael J. Flynn wrote:
> On Thu, 23 Dec 1999, Sean /The RIMBoy/ wrote:
>
> > ls -la | grep /dev/printer
> >
> > and see what it returns. If it returns
> >
> > /dev/printer blah blah > /dev/lp1
> >
> > or something to that effect, make a new link to /dev/lp0. Or, do what I
> > do, skip /dev/printer and go straight for the device in your printcap.
> > fixing a 0 or 1 in printcap is easier (IMHO) than resetting the sym link
> > in /dev.
>
> Sean-
>
> I took a look at the device files and /dev/printer is not a symbolic link
> to an lp device. Doing a file on it also indicates that it is a socket
> and not a character device. Have no idea why the file is a socket.
Because it's a socket that it's supposed to be! Or at least, it's a
socket that papd expects it to be. It's the socket by which papd says to
lpd 'Here you go, here's a new print job'. On systems (like mine) where
lpd doesn't seem to listen on /dev/printer, this doesn't work, so I had to
shift to the 'lp=|lpr' approach.
If, on some distributions, /dev/printer is a link to one of the printer
devices, then that muddies the waters still further :-) It's no wonder
different people are seeing some different behaviours of papd..
Jules
/----------------+-------------------------------+---------------------\
| Jelibean aka | [EMAIL PROTECTED] | 6 Evelyn Rd |
| Jules aka | [EMAIL PROTECTED] | Richmond, Surrey |
| Julian Bean | [EMAIL PROTECTED] | TW9 2TF *UK* |
+----------------+-------------------------------+---------------------+
| War doesn't demonstrate who's right... just who's left. |
| When privacy is outlawed... only the outlaws have privacy. |
\----------------------------------------------------------------------/
