From: spcapt1@ananta.spc.uchicago.edu (Allen Todd) Subject: Re: (The return of) problem waking lpd. Date: Tue, 8 Jun 1993 22:52:21 GMT
In article <1993Jun8.163349.376@ludens.elte.hu> mentler@ludens.elte.hu writes:
>In article <1993Jun7.232621.1@vax1.bham.ac.uk>, mccauleyba@vax1.bham.ac.uk (Brian McCauley) writes:
>> I've been trying to work out some pattern to when lpc gernerates the
>> message:
>>
>> lpc: connect: no such file or directory
>>
>> or when lpr fails to start the daemon. These seem to be connetced
>> in some wat with each other and with the socket that is sometimes
>> called /dev/printer and sometimnes /tmp/.printer. (I don't really
>> know anything about sockets so I'm lost). I used to get this problem
>> with Ross Biro's old lpd package but I managaged to get rid of it
>> now I have the lpd from net-2 the problem has returned. It doesn't happen
>> very often and killing and restarting lpd a few times seems to bring it back.
>> This porblem appears even when running as root and is intermittent so
>> it doesn't look like file permissions to me.
>>
>> I expect this is a bug in socket support and would be fixed if I got the whole
>> of net-2 but I'm not up to that much hassle yet. If this is the case could
>> someone let me know.
>>
>> If I could get a good answer to this question I could put in the next release
>> of the lpd-FAQ which is just about ready now.
>> --
>I have had this problem for a long time. Than I installed the TCP/IP package
>and the problem had gone.
>
>Mentler Gyula (from Hungary)
>
Since I do not have a networked system, I can only guess that installing the
TCP/IP package installed an /etc/services file to manage the network
connections. People using SLS with network support compiled into the
kernel but not installing the networking software may see this problem with
the lpd daemon. As I mentioned in an earlier post, adding an /etc/services
file solved the problem for me even though I do not use any network services.
It contained only the following line, although it probably(?) wouldn't
hurt to put a complete /etc/services in.
printer 515/tcp spooler # line printer spooler
What tipped me off was turning on syslogd and syslogkd and one of them
reported that lpd could not find its TCP/IP conection.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Allen Todd spcapt1@ananta.spc.uchicago.edu
Social Science and Public Policy Computing Center University of Chicago