l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2001 Dec 30 17:14

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] LPRng ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] LPRng ?

begin Ajay <lugod@os2man.cjb.net> 
> Hola guys,

> :1. have you started the spooler daemon using verbose logging?  that would be
> :   the first step.  by default, it's not turned on.
> 	No, I haven't.  I did try either lpr or lp with verbosity, and I
> wasn't sure what to do with that, it printed a LOT of info.  I'd assume the
> server (lpd) would do the same?  But I'll check that out.
ok.  but that should be the starting point.   :)

> :2. have you looked at logs for both client and server?
> I can find no logs on the server, even though I see the lf= on the server's
> printcap file.
 there *has* to be logs on the server.  on debian, it should go under

a thought -- is your spooler daemon tcpd wrapped?  look at /etc/hosts.deny.
most people say ALL: ALL, in which case you MUST open lpd up in
/etc/hosts.allow since hosts.allow is checked first.   if the daemon "just
runs" instead of being called by inetd, then:

1. kill the daemon
2. go to a **virtual console**.  this is important.  messages don't usually
   get sent to non-login shells.
3. run the spooler daemon with whatever verbose switches there are.
4. try to run the job on the client machine.  see what happens.

this has the benefit that we just short-circuited syslogd.  messages should
go straight to the console.  better yet, tack on a 2>printer.log at the end
of the command.

don't forget to rerun inetd startup script if you change the wrapper files.
don't forget to rerun lpd startup script if you change lpd config files.
they prolly read the files on the fly, but ya never know...

if lpd isn't reporting to any log files, that is just phracked up, majorly.
look at /etc/syslogd.conf to see where lpd logs should be going.

> And incase it wasn't clear from the previous message, logging into the
> server and printing a file works fine,


> reason doesn't want to allow clients to connect/print/whatever.  Any other
> thoughts appreciated, otherwise I'll try the Debugging/Verb output when I
> get a chance a little later.

it all hinges on what the logs say.  people like to say "use the source" is
the watchphrase of the open source movement.  bullwacky.  "use the logs" and
"use the deja" are more like it!

> :               ** Please don't send me html email **
>I found a site that has procmail rules to auto bounce that, if interested..  ;)

nah.  already written.  :-)   i've been reading a book on .procmail that i
got at nerdbooks.  it gets high recommendations; i'm thinking the club should
have a copy for loans.  it's that good.


PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E  70A9 A3B9 1945 67EA 951D
PGP Public Key:  finger p@dirac.org
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.