Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Nov 2001 00:48:51 -0500
From:      Garance A Drosihn <drosih@rpi.edu>
To:        what ever <thursday@freeshell.org>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: lpd: only root can print
Message-ID:  <p05101000b820edba01c1@[128.113.24.47]>
In-Reply-To: <20011121014427.A15466@sdf.freeshell.org>
References:  <20011120211245.A17671@sdf.freeshell.org> <20011120161504.R53181-100000@malkav.snowmoon.com> <20011121003157.G87336@mars.thuis> <20011121014427.A15466@sdf.freeshell.org>

next in thread | previous in thread | raw e-mail | index | archive | help
At 1:44 AM +0000 11/21/01, what ever wrote:
>Hi,
>
>I gave this a try, but still no luck.
>
>I'm thinking it must be something with master.passwd, passwd, or pwd.db?

I've been watching your questions go by, but offhand I can't think of
anything which would cause that behavior.  I can imagine it working
for root and not working for *everyone* else, but I can't figure why
a new userid would work and an old one wouldn't.

Earlier you had done a:
>	ls -lF /var/spool/lpd
>	drwx------  2 daemon  daemon  512 Dec  7  2000 lp/
>
.	I chmod'd this to 770, and still have the problem.

What do you get from:
     ls -lFd /var/spool /var/spool/lpd
     ls -lF /var/spool/lpd/lp

Try running /usr/sbin/chkprintcap, and see if it tells you anything
interesting.

Check all your environment settings.  In bash, that would be done by
just typing:    set | more
and watching what goes by.  I'm not sure what you'd need to look for,
but maybe something would pop up.  I think the only variable which
*should* make any difference is the value of PRINTER.

Actually, another thing to check is your PATH setting.  See which
lpr you are getting, and if there are more than one.  In bash, the
command of interest might be 'type -a lpr'.  Try it as yourself,
and as one of the userid's where lpr is working.  Once you find
whichever lpr you're using, do an 'ls -l' on that, to see who owns
it and how it is permitted.

Can your userid do an 'lpq'?
It hangs if you do an 'lpr file'.  What if you do an 'lpr -Plp file'?
(or whatever your specific printer queue is named).  What happens if
you do an 'lpr -Pbogus file' (specifying a print queue that does NOT
exist).

That's about all the ideas I have.

-- 
Garance Alistair Drosehn            =   gad@eclipse.acs.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101000b820edba01c1>