Visit Our UNIX and Linux User Community

Full Discussion: qdsemon
Top Forums UNIX for Dummies Questions & Answers qdsemon Post 16672 by killerserv on Tuesday 5th of March 2002 08:06:23 PM
Old 03-05-2002
Use the command ps -ef | grep qdaemon to verify that the qdaemon is not active. If the qdaemon is not active, you should see, at the most, a line of output representing the grep itself. It should look something like this:

root 2992 18792 0 12:46:39 pts/2 0:00 grep qdaemon

If the qdaemon is active, which it almost certainly will not be, you will see a variant of the following line:

root 2980 3652 0 12:41:25 - 0:00 /usr/sbin/qdaemon

If the qdaemon is not active, issue the command startsrc -s qdaemon to restart the qdaemon. If the qdaemon died, it should have been restarted automatically by the srcmstr process, but it doesn't always work, so restart it manually. You should see a variant of this message:

0513-059 The qdaemon Subsystem has been started. Subsystem PID is 3000.

Wait one minute or so and re-issue the command ps -ef | grep qdaemon. Is the qdaemon still active or did it just start and then die? If the qdaemon is no longer active, despite the fact that you just restarted it and received a message stating the qdaemon's process id (PID) and that it was active, check for the existence of the file named /var/spool/lpd/stat/pid. You can do this by issuing the command cat /var/spool/lpd/stat/pid. This file contains the PID of an active qdaemon. When the qdaemon is not active, the file is supposed to be removed.
 
Test Your Knowledge in Computers #605
Difficulty: Medium
As of MySQL 8.0.14, the ADD DATAFILE clause of the CREATE TABLESPACE statement is mandatory.
True or False?
LPRM(1) 						    BSD General Commands Manual 						   LPRM(1)

NAME
lprm -- remove jobs from the line printer spooling queue SYNOPSIS
lprm [-] [-P printer] [-w maxwait] [job# ...] [user ...] DESCRIPTION
lprm will remove a job, or jobs, from a printer's spool queue. Since the spooling directory is protected from users, using lprm is normally the only method by which a user may remove a job. The owner of a job is determined by the user's login name and host name on the machine where the lpr(1) command was invoked. Options and arguments: -Pprinter Specify the queue associated with a specific printer (otherwise the default printer is used). -w maxwait Specify the maximum time to wait in seconds for remote responses. The default is 300 seconds or 5 minutes. - If a single '-' is given, lprm will remove all jobs which a user owns. If the super-user employs this flag, the spool queue will be emptied entirely. user Causes lprm to attempt to remove any jobs queued belonging to that user (or users). This form of invoking lprm is useful only to the super-user. job # A user may dequeue an individual job by specifying its job number. This number may be obtained from the lpq(1) program, e.g. % lpq -l 1st:ken [job #013ucbarpa] (standard input) 100 bytes % lprm 13 If neither arguments or options are given, lprm will delete the currently active job if it is owned by the user who invoked lprm. lprm announces the names of any files it removes and is silent if there are no jobs in the queue which match the request list. lprm will kill off an active daemon, if necessary, before removing any spooling files. If a daemon is killed, a new one is automatically restarted upon completion of file removals. ENVIRONMENT
If the following environment variable exists, it is used by lprm. PRINTER If the environment variable PRINTER exists, and a printer has not been specified with the -P option, the default printer is assumed from PRINTER. FILES
/etc/printcap Printer characteristics file. /var/spool/output/* Spooling directories. /var/spool/output/*/lock Lock file used to obtain the pid of the current daemon and the job number of the currently active job. DIAGNOSTICS
``Permission denied'' if the user tries to remove files other than his own. SEE ALSO
lpq(1), lpr(1), lpd(8) HISTORY
The lprm command appeared in 3.0BSD. BUGS
Since there are race conditions possible in the update of the lock file, the currently active job may be incorrectly identified. BSD
June 6, 1993 BSD

Featured Tech Videos

All times are GMT -4. The time now is 01:06 AM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy