From: jhh@scss3.cl.msu.edu.noname (John Hayes) Subject: Re: lpr: connect: No such file Date: 10 Aug 1993 14:38:15 GMT
In article 594@sun1.clark.net, ganderson@clark.net (Gary Anderson) writes:
> Matthew Aaron Wormley (mwormley@galaxy.csc.calpoly.edu) wrote:
> : >: In article <23oe9rINNclh@tom.rz.uni-passau.de>, claussen@db.fmi.uni-passau.de (Jens Claussen) writes:
> : >: >
> : >: > lpr: connect: No such file or directory
> : >: > jobs queued, but cannot start daemon.
> : >: >
> : >: > the lpd daemon is not runnig, though started in rc.inet2.
> : >: >
> : >: > The question ist contained in the lastest FAQ, but without an answer.
> : >
>
> : Check the permissions on your lp? files and then be sure that the
> : spool directory listed in your /etc/printcap file exists.
>
> : worm
>
> Subject: Re: lpr: connect: No such file
> Newsgroups: comp.os.linux
> References: <12973@obelix.icce.rug.nl> <23oe9rINNclh@tom.rz.uni-passau.de> <1993Aug4.180945.1@vms1.bham.ac.uk> <1993Aug8.013906.15469@datasoft.north.net> <1993Aug08.224911.2987@rat.csc.calpoly.edu>
> Organization: Clark Internet Services, Inc., Ellicott City, MD USA
>
> Matthew Aaron Wormley (mwormley@galaxy.csc.calpoly.edu) wrote:
> : >: In article <23oe9rINNclh@tom.rz.uni-passau.de>, claussen@db.fmi.uni-passau.de (Jens Claussen) writes:
> : >: >
> : >: > lpr: connect: No such file or directory
> : >: > jobs queued, but cannot start daemon.
> : >: >
> : >: > the lpd daemon is not runnig, though started in rc.inet2.
> : >: >
> : >: > The question ist contained in the lastest FAQ, but without an answer.
> : >
>
> : Check the permissions on your lp? files and then be sure that the
> : spool directory listed in your /etc/printcap file exists.
>
> : worm
>
> I'm also having trouble with lpr/lpd. I used to get the
> 'lpr: connect: no such file or directory' error. I created the
> var/spool/lpd directory.
> Now I get the error 'lpr: connect: invalid argument'. Like the rest
> of you, my lpd daemon starts up in rc.inet2, and is shown by 'ps -aux', but I
> still
> get 'jobs queued, but unable to start daemon', even though the system says
> 'lpd' is sitting there. I've confirmed that the lock file is being created
> in var/spool/lpd. Two other things I've noticed, that I've not seen mentioned
> by any of the other folks having lpr/lpd problems:
> 1.) lpr work fine (i.e. printing commences automatically) IF I'm logged
> on as a regular user (NOT as root).
> 2.) If I'm logged on as root, and try to use lpr, of course I get the
> above errors, and no print. BUT, if I go into lpc, and do a
> restart lp1, printing starts.
>
> For the most part, my lp* files (i.e.-lpd lpr, lpc, etc.) are all set
> to permissions as shown in the 'how-to-print' faq from, I think, G. Taylor,
> at god.hounix.com. Where my setup diverges, though, is owner/group.
> The FAQ says that the NET-2 stuff sets them to lp /lp. that's not quite
> right. It sets them (for the most part) to root/lp.
>
> Here's the rest of my configuration:
> '486 clone
> SLS 1.02
> p.l. 10 kernel
> gcc 2.4.3
> libs 4.4.1
> NET-2 stuff installed (slip working, albeit with a small problem, to be
> the topic of another posting)
>
> Hope this is enough detail for someone to figure out what might be
> going wrong. It sure looks like alot of us are having the same problem !
>
>
I'm having a similar problem with an odd twist - first let me state some particulars
about my system configuration:
SLS1.02
XFree86 1.3
libc.so.4.4.1
Linux 0.99pl10
Net2
Now for the particulars:
1. When Linux boots up and there are jobs in the printer queue they get printed.
2. When root prints a job, any other jobs in the printer queue get printed.
3. If root kills lpd and restarts it, any jobs in the printer queue get printed.
4. If any other user prints a job, the error message describe above is reported -
however, the job is entered in the queue to be printed explaing behaviors described
in 1, 2 & 3.
Lpd is loaded and running, it will only print when root makes a print request - and
then it prints all of the past spooled jobs.
I've been slowly checking on permissions and directories - I'm still examining things,
however, I've seen so many messages on my very problem and not seen any one describe
all of the auxilliary conditions that I've encountered that I thought it was worth
making a report/observation.
I've listed enough information that some may say "I believe I know what the problem
is".
Please don't refer me to the faq! As I said, I've been working at it slowly. I started
out with SLS 1.02 and had upgraded everything I possibly could to current levels, i.e.
that were current when I was in the mood - I've currently gotten out of the mood as
there were to many problems with the initial release of the net2 stuff. I decided to
wait for more upgrades until the net stuff is more stable. When I upgraded the net2
stuff I had a pre release net2 faq - things have changed a lot since then.
If you can't provide any information that could result in a fix don't bother to
respond - from the recurring theme it sounds like some people are really having a
printer problem!
Before anybody asks - I installed gcc 4.4.5 or whatever the newest available version
was - so my compiler shouldn't be a problem.
Thanks, John Hayes