04-19-2008
There are too many different lpd implementations to answer this with any certainty. Maybe you can follow up with more details about your platform. In general, I would say most lpd daemons are smart enough to not clear the spool; that's why they have one. There might be a problem if a job is being printed so maybe you should put all jobs on hold before restarting just to be on the safe side.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am attempting to setup an IP based printer in a SCO environment. It is a cognitive printer. I attempted to add it via the HP interface but I could not get anything sent from the spooler to the printer in SCO?
My questions is or are should this be setup as a local or remote printer? When I... (6 Replies)
Discussion started by: spglass
6 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I am using Solaris 8 and have several printers (HP lasers or inkjets) connected behind PCs, printing thus being controlled by LPD.
All I can print is ASCII, not very keen, no images, no boxes etc.
Is there any thread (I assure, I have been searching!) or discussion explaning how to set... (0 Replies)
Discussion started by: nulnul7
0 Replies
3. SCO
Hi.
I'm receive thats error on my PC.
lp: cannot lock /usr/spool/lpd/printer1/.seq
This PC is a Windows pc running lpd on port 515.
That its means?
Thanks.
PD. Sorry for my english! (0 Replies)
Discussion started by: sebpes
0 Replies
4. Red Hat
Hi,
Can you please clear me the difference between restarting the daemon and the service. To be more clear,
/etc/init.d/mysqld restart
and
/etc/init.d/mysqld restart
What is the difference on this both two?..... (4 Replies)
Discussion started by: gsiva
4 Replies
5. SCO
Dear All,
I have configured a printer on a unix box to be printing on windows xp printer. Below are the steps followed:-
Create the printer on the Windows XP box and share it as prt5
Enable unix printer services on windows XP box
On unix box i make changes on hosts,hosts.equiv and .rhosts... (1 Reply)
Discussion started by: njoroge
1 Replies
6. SCO
hi
Howto replace Line Printer Daemon (LPD) with CUPS on SCO 5.0.6? (3 Replies)
Discussion started by: ccc
3 Replies
7. Solaris
Apologies in advance, I'm usually a Linux admin so I'm not well versed in Solaris administration.
In Linux there's usually an lpd executable running and you can check the process list for it to do a high level check on the state of the printing subsystem. Is the executable called the same in... (1 Reply)
Discussion started by: thmnetwork
1 Replies
8. Solaris
Hi guys,
one of my services in solaris 10 is in maintenance mode. When I checked why, the reason is that the service is "restarting too quickly."
# svcs -x svc:/application/management/snmpdx:default
svc:/application/management/snmpdx:default (Sun Solstice Enterprise Master Agent)
State:... (2 Replies)
Discussion started by: cjashu
2 Replies
LPQ(1) General Commands Manual LPQ(1)
NAME
lpq - spool queue examination program
SYNOPSIS
lpq [ +[ n ] ] [ -l ] [ -Pprinter ] [ job # ... ] [ user ... ]
DESCRIPTION
lpq examines the spooling area used by lpd(8) for printing files on the line printer, and reports the status of the specified jobs or all
jobs associated with a user. lpq invoked without any arguments reports on any jobs currently in the queue. A -P flag may be used to spec-
ify a particular printer, otherwise the default line printer is used (or the value of the PRINTER variable in the environment). If a +
argument is supplied, lpq displays the spool queue until it empties. Supplying a number immediately after the + sign indicates that lpq
should sleep n seconds in between scans of the queue. All other arguments supplied are interpreted as user names or job numbers to filter
out only those jobs of interest.
For each job submitted (i.e. invocation of lpr(1)) lpq reports the user's name, current rank in the queue, the names of files comprising
the job, the job identifier (a number which may be supplied to lprm(1) for removing a specific job), and the total size in bytes. The -l
option causes information about each of the files comprising the job to be printed. Normally, only as much information as will fit on one
line is displayed. Job ordering is dependent on the algorithm used to scan the spooling directory and is supposed to be FIFO (First in
First Out). File names comprising a job may be unavailable (when lpr(1) is used as a sink in a pipeline) in which case the file is indi-
cated as ``(standard input)".
If lpq warns that there is no daemon present (i.e. due to some malfunction), the lpc(8) command can be used to restart the printer daemon.
FILES
/etc/termcap for manipulating the screen for repeated display
/etc/printcap to determine printer characteristics
/usr/spool/* the spooling directory, as determined from printcap
/usr/spool/*/cf* control files specifying jobs
/usr/spool/*/lock the lock file to obtain the currently active job
SEE ALSO
lpr(1), lprm(1), lpc(8), lpd(8)
BUGS
Due to the dynamic nature of the information in the spooling directory lpq may report unreliably. Output formatting is sensitive to the
line length of the terminal; this can results in widely spaced columns.
DIAGNOSTICS
Unable to open various files. The lock file being malformed. Garbage files when there is no daemon active, but files in the spooling
directory.
4.2 Berkeley Distribution June 5, 1986 LPQ(1)