My original Question:
> Dear Fellow Managers,
>
> I have an AlphaServer 2100 system running Digital UNIX 4.0B and I am having the
> following problems.
>
> When I submit the lpr -P<printer> <filename> command I get the following error
> message.
>
> lpr: connect: No such file or directory. Jobs queued but cannot start daemon.
>
> I checked the locks files, the permissions to /usr/lbin and to /usr/lbin/lpd, I
> checked the permissions of all the lpd*err files. All looks fine, but I still
> get the same problem everytime I try the lpr command.
>
> If I should then enter the /usr/lbin/lpd command by hand, all outstanding print
> jobs will print and then lpd would die.
>
> When I try to start lpd by using the command, /sbin/init.d/lpd start , it does
> not seem like lpd starts at all. The only thing unusual that I have noticed
> (when comparing against another similar system) is that the file /dev/printer is
> missing. Is this normal? If it is not normal, then how do I re-create that
> file?
>
> What else can I check to get this problem fixed?
>
It would seem that either my statement of the problem was not clear enough or
this is not such an easy problem to solve as all that. Nevertheless, I got one
reply from George Gallen <ggallen_at_slackinc.com> who gave me a command to try
and observe the result. He said,
"What happens if you do:
cat filename | lp -dPRINTERNAME "
Unfortunately, since the LPD is not running, that command fails. It says no
daemon active, but the file was queued to print.
Thus far the system cannot print unless an operator or system manager
periodically enters the command,
/usr/lbin/lpd
by hand. When he does this, the system will print all enqueued jobs and then
cannot print again until someone enters that command again.
Received on Fri Jun 18 1999 - 18:50:02 NZST