root@VLSI-MENTOR.JPL.NASA.GOV (The vlsi-mentor Super User) (06/08/90)
Well, this is another good one. Check this out: $ lpc lpc> up all lp: lpc: connect: No such file or directory couldn't start daemon laser: lpc: connect: No such file or directory couldn't start daemon What does this cryptic message mean? I've checked all the files /usr/spool/lpd, /etc/printcap, /usr/spool/lpd/servername. Llbd is running. Halp! ---- Dave Hayes dave@vlsi-mentor.jpl.nasa.gov dave%vlsi-mentor@jpl-mil.jpl.nasa.gov "The word 'choice' is a fraud when one is taught what to choose."
rees@dabo.ifs.umich.edu (Jim Rees) (06/08/90)
In article <9006072231.AA06791@vlsi-mentor.jpl.nasa.gov>, root@VLSI-MENTOR.JPL.NASA.GOV (The vlsi-mentor Super User) writes: > $ lpc > lpc> up all > lp: > lpc: connect: No such file or directory > couldn't start daemon Are you sure TCP is running? Also, you might try setting the environment variable APOLLO_STATUS to 'true'. This will cause perror() to give you a somewhat more descriptive error message.
root@VLSI-MENTOR.JPL.NASA.GOV (The vlsi-mentor Super User) (06/09/90)
me> $ lpc me> lpc> up all me> lp: me> lpc: connect: No such file or directory me> couldn't start daemon > Are you sure TCP is running? > Also, you might try setting the environment variable APOLLO_STATUS to 'true'. > This will cause perror() to give you a somewhat more descriptive error message. $ lvar environment SYSTYPE = bsd4.3 environment PROCESSNAME = root.bc35.0 environment APOLLO_STATUS = true environment PATH = /usr/lib/newsbin:/usr/ucb:/bin:/usr/bin:/etc:/usr/apollo/bin $ pst ------------------------------------------------------------ Node: 2146B Time: Friday, June 8, 1990 1:42:18 pm (PDT) ------------------------------------------------------------ Processor | PRIORITY | Program | State | Process Name Time (sec)| mn/cu/mx | Counter | | ------------------------------------------------------------ 93541.178 -- -- -- -------- ----- <Null Process> 1040.050 -- -- -- -------- ----- <Aegis Processes> 31.203 16/16/16 3B428288 Wait init 0.137 3/14/14 <active> Ready uid = 4AE26514.D002146B (pst) 1.386 3/13/14 3B428288 Wait root.bc35.0 1.400 3/14/14 3B42814A Wait root.bc35 0.130 3/14/14 3B42814A Wait llbd 9.956 3/14/14 3B42814A Wait pad01 11.422 3/14/14 3B42814A Wait alarm_server 1.447 3/14/14 3B427C8A Wait mbx_helper 172.767 16/16/16 3B42814A Wait display_manager 17.061 3/13/14 3B42814A Wait server_process_manager 402.944 3/15/15 3B427DF2 Wait uid = 4AD938D6.6002146B (cdsServer) 567.114 3/14/14 3B42814A Wait tcpd ----------- 95798.203 $ lpc lpc> up all lp: lpc: connect: No such file or directory couldn't start daemon laser: lpc: connect: No such file or directory couldn't start daemon lpc> quit I did check the obvious. Perhaps there is another way to make lpc print out more meaningful error mesages? ---- Dave Hayes dave@vlsi-mentor.jpl.nasa.gov dave%vlsi-mentor@jpl-mil.jpl.nasa.gov "The word 'choice' is a fraud when one is taught what to choose."
smhall@peg.UUCP (06/12/90)
Could it be that lpd doesn't like your printer entry in /etc/printcap - try "lp=/dev/display" to debug a printer. That will dump the spooled file to a printer and make lpd happy if it is the device that it couldn't connect to. Steve Hall, HP/Apollo SE Brisbane, Australia
kdavis@bert.HYWLMSD.WA.COM (Karen Davis) (06/14/90)
I have seen this error message when I first installed sr10. I found that each node must have a /usr/spool/<printer name> directory and can not link to the tcp_admin node. Also, diskless nodes can not run lpd. Karen Davis Honeywell MSD (206) 356-3439