home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ulowell!news.bbn.com!usc!nic.csu.net!vmsb.is.csupomona.edu!cvadr021
- Newsgroups: comp.os.linux
- Subject: Re: Getting lpr/lpd to work
- Message-ID: <1992Dec27.093240.1@vmsb.is.csupomona.edu>
- From: cvadr021@vmsb.is.csupomona.edu
- Date: 27 Dec 92 09:32:40 PST
- References: <Bzw8pz.EM5@utdallas.edu>
- Organization: California State Polytechnic University, Pomona
- Nntp-Posting-Host: acvax2
- Nntp-Posting-User: cvadr021
- Lines: 26
-
- In article <Bzw8pz.EM5@utdallas.edu>, ramesh@utdallas.edu (R. Ramesh) writes:
-
- > I can lpr files (as root) which get moved to appropriate directory. As
- > ordinary user, I cannot even lpr files as I get
-
- > lpr: cannot create /usr/spool/lp/.seq
- >
- If /usr/spool/lp/.seq does not exist, lpr creates it. Unfortunately,
- it belongs to the user not the daemon. (is this a bug?) When you lpr
- something as root, you create the .seq file as owned by root and no one else
- can print. Go into /usr/spool/lp and chmod 666 .seq
-
- >
- > I have lpr with setgid bit and lpr is chowned to daemon.daemon.
- >
- > lpc cannot do any thing. It always complains lp: cannot restart daemon.
- > It looks to me some permission problem unless you see something different.
- > Could some one that set up lp properly tell me what permissions are needed
- > for various support files.
- >
- > Ramesh
- >
- --
- ---
- David Dhuyvetter
- email: cvadr021@csupomona.edu
-