Date: Wed, 21 Nov 2001 06:04:25 +0000 From: what ever <thursday@freeshell.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-questions@freebsd.org Subject: Re: lpd: only root can print Message-ID: <20011121060425.A15686@sdf.freeshell.org> In-Reply-To: <p05101000b820edba01c1@[128.113.24.47]>; from drosih@rpi.edu on Wed, Nov 21, 2001 at 12:48:51AM -0500 References: <20011120211245.A17671@sdf.freeshell.org> <20011120161504.R53181-100000@malkav.snowmoon.com> <20011121003157.G87336@mars.thuis> <20011121014427.A15466@sdf.freeshell.org> <p05101000b820edba01c1@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you for your thoughtful advise. It turns out that my problem was with my $PATH, which was set in my .bashrc. I found that when removing my .bashrc & reloging in, printing would work fine. Further investigation revealed that /usr/local/bin appeared in my path BEFORE /usr/bin. My recent install of kde-2.2 (If anyone can tell me how to run this without fam, please mail me) installed cups-1.1.10.1, which installed an lpr executable in /usr/local/bin, which I of course was hitting since /usr/local/bin appeared in my path before /usr/bin. I am an idiot. After a moment of panic thinkinking that my machine had been cracked, I realized the kde connection. In other news, I am *still* trying to get sound working. I've managed to get the os to recognize the card, but catting a file to /dev/dsp0 always reports device busy after about 1/2 a second of sound...and kde's sound server always reports the device as busy... On Wed, Nov 21, 2001 at 12:48:51AM -0500, Garance A Drosihn wrote: > 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 -- thursday@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org 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?20011121060425.A15686>