AREA:COMP.OS.LINUX
From: wto@cbnewsg.cb.att.com (William T. O Connell)
Organization: Peripheral Control Development group
In article <1993Mar25.205437.5381@primerd.prime.com> cummings@hammer.prime.com
(Kevin Cummings) writes:
(Guenther Seybold) writes:
prints
I usually respond by e-mail to eliminate some traffic but, I have responded
to a few lately of this nature - so maybe there are many with this problem?
This typical happens due to a few things - lpd was never started up,
bad entries in the /etc/printcap file, wrong permission settings,
wrong owner or group settings, or missing files and directories, etc ...
I keep a history file of things that I do - the following paragraph
is an extract from it that I just pulled out of the file. It was what
I wrote when I installed the lpr package a few months ago. - it lists the
things I did.
+ 8) This package is real picky. All executables were changed to 2755,
+ and owned by daemon. Checked proper permissions on all directories,
+ i.e. /usr/spool, /usr/spool/lp1, (all 755 - owned by daemon)
+ and files i.e. /usr/spool/lp1/.seq which is now 664 owned by daemon.
+ Ensure printcap has valid command options for printer.
+ lpd should be started in rc.local (will startup then
+ go away - rewoken up by lpr).
The following is the permissions and ownerships for some key directories
and files - the ownership does make a difference on some of them!
/etc# ls -l lp*
-rwxr-sr-x 1 daemon daemon 21508 Nov 19 23:32 lpc*
-rwxr-sr-x 1 daemon daemon 37892 Jan 1 13:38 lpd*
-rwxr-sr-x 1 daemon daemon 17412 Nov 19 23:32 lpr*
/usr# ls -l
drwxrwxr-x 10 root root 176 Mar 25 22:03 spool/
/usr/spool#
drwxrwxr-x 2 daemon daemon 160 Mar 24 00:09 lp1/
-rw-r--r-- 1 root daemon 3 Mar 25 22:03 lpd.lock
/usr/spool/lp1# ls -al
total 5
drwxrwxr-x 2 daemon daemon 160 Mar 24 00:09 ./
drwxrwxr-x 10 root root 176 Mar 25 22:03 ../
-rw-rw-r-- 1 daemon daemon 4 Mar 24 00:09 .seq
-rw-r--r-- 1 daemon daemon 3 Mar 25 22:03 lock
-rw-r--r-- 1 daemon daemon 25 Mar 24 00:09 status
I might of missed some of the things that you should check for,
but, I hope this helps anyone still having problems with the
lpr package.
- Bill O'Connell
Previous message: [thread] [date] [author] Next message: [thread] [date] [author]
Messages in current thread:
Problems with lpr: It can't.., William T. O Connell, (Fri Mar 26, 7:40 pm)