I did run checkpc -f, who created the right entries. This is just a typo in the mail (you are right, the entry is /var/spool/lpd/lp), I didn't cut & paste the file to my mail. Anyway the trouble is always present... some output from commands (maybe this will clarify things...) First, I launch a new print job: # lpr /etc/printcap Next, I look in the queue: # lpq -ll Printer: lp@daffy Queue: 1 printable job Server: pid 7212 active Rank Owner/ID Class Job Files Size Time 1 root@daffy+211 A 211 /etc/printcap 60 15:22:52 # lpq -v Printer: lp@daffy Job: root@daffy+211 Printing: no Aborted: no Spooling: no Queue: 1 printable job Server: pid 7212 active SPOOLCONTROL= Job: root@daffy+211 status= 1 Job: root@daffy+211 size= 60 Job: root@daffy+211 time= 0x3d36c12c Job: root@daffy+211 CONTROL= Aroot@daffy+211 CA D2002-07-18-15:22:58.132 Hdaffy.plasky.eft.be J/etc/printcap Lroot Proot Qlp N/etc/printcap fdfA211daffy.plasky.eft.be UdfA211daffy.plasky.eft.be Job: root@daffy+211 HOLDFILE= A=root@daffy+211 C=A D=2002-07-18-15:22:58.132 datafile_count=1 datafiles=N/etc/printcapfdfA211daffy.plasky.eft.beUdfA211daffy.plasky.eft. be file_hostname=daffy.plasky.eft.be filenames=/etc/printcap H=daffy.plasky.eft.be held=0x0 hf_name=hfA211 hold_class=0x0 hold_time=0x0 J=/etc/printcap job_time=0x3d36c12c job_time_usec=0x1e5b9 L=root number=211 P=root priority=A Q=lp size=60 transfername=cfA211daffy.plasky.eft.be update_time=2002-07-18-15:22:58.132 # lpc status all Printer Printing Spooling Jobs Server Subserver Redirect Status/(Debug) lp@daffy enabled enabled 1 7212 none issuing a top show this (part of the screen) ----CUT------- 7212 lp 18 0 6560 6560 1876 R 96,7 2,5 3:32 lpd 5364 cbk 9 0 2756 2756 2160 R 1,9 1,0 3:40 smbd 7250 root 13 0 1080 1080 836 R 0,9 0,4 0:00 top 1106 named 9 0 5164 5048 1672 S 0,1 1,9 0:22 named 1 root 8 0 116 72 72 S 0,0 0,0 0:00 init 2 root 9 0 0 0 0 SW 0,0 0,0 0:00 keventd 3 root 19 19 0 0 0 RWN 0,0 0,0 0:00 ksoftirqd_CPU0 4 root 9 0 0 0 0 SW 0,0 0,0 0:07 kswapd 5 root 9 0 0 0 0 SW 0,0 0,0 0:00 kreclaimd 6 root 9 0 0 0 0 SW 0,0 0,0 0:01 bdflush 7 root 9 0 0 0 0 SW 0,0 0,0 0:02 kupdated 11 root 9 0 0 0 0 SW 0,0 0,0 0:00 scsi_eh_1 12 root 9 0 0 0 0 SW 0,0 0,0 0:00 scsi_eh_2 462 root 9 0 220 164 120 S 0,0 0,0 0:01 syslogd 467 root 9 0 980 772 356 S 0,0 0,3 0:00 klogd 569 nobody 9 0 216 160 124 S 0,0 0,0 0:00 apcsmart ----CUT------- For information, trying to kill the job from lpc won't work, as lpc tries to respawn the job directly. I must perform a lpc down and then a lpc kill, then empty the queue issuing lprm. I've included the original printcap file, for the sake of clarity. # cat /etc/printcap lp :sd=/var/spool/lpd/lp :lp=hp5m.plasky.eft.be%9100 :mx=0 Annoying isn't it? -----Original Message----- From: phillip.griffith@srs.gov [mailto:phillip.griffith@srs.gov] Sent: jeudi 18 juillet 2002 13:53 To: lprng@lprng.com Subject: Re: LPRng: lpd process running foolish lp :sd=/var/spool/lp/lpd <== should be /var/spool/lpd/lp? :lp=printer_FDQN%9100 :mx=0 Did you run checkpc? This is an LPRng command to validate your printcap. Phillip Griffith (803) 952-8776 Information Technology Department Westinghouse Savannah River Company ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to majordomo@lprng.com (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to majordomo@lprng.com with: | example: subscribe LIST | subscribe lprng-digest myname@host.org unsubscribe LIST | unsubscribe lprng myname@host.org If you have major problems, send email to papowell@astart.com with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------