Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!milton!etb@milton.u.washington.edu From: etb@milton.u.washington.edu (Eric Bushnell) Newsgroups: comp.sys.apollo Subject: Re: Beware Sr10.3 Keywords: sr10.3 Message-ID: <17856@milton.u.washington.edu> Date: 6 Mar 91 22:57:30 GMT References: <2300@ccadfa.adfa.oz.au> <17825@milton.u.washington.edu> Sender: etb@milton.u.washington.edu Organization: University of Washington, Seattle Lines: 42 >In article <2300@ccadfa.adfa.oz.au> iaf@ccadfa.adfa.oz.au (- Mathematics) writes: >> >> Question: Does anyone out there use lpd and have printers >> directly connected to apollo sio lines? > >I have a laserjet 3 connected as plain line printer (waiting for >a PostScript cartridge) driven by lpd. I use a basic 4-wire serial >cable, and the plain lp printcap entry. This is only one node, > >I have had trouble getting lpd to work on the same node that the >Aegis print software runs on, but I haven't played with that >combination enough to know how serious a problem it is. >> Since then, I have tried getting lpd to run on my token ring, which has a 10.3 node as print manager and server. Sure enough, it didn't work. The prsvr locks /dev/sio1, so a printcap spec of lp=/dev/sio1 on that host reports device busy. (Makes sense) I tried running the lpd on another host, with a printer on the sio1 port. Then lpr reports "no daemon present." Apparently the master lpd won't fork properly. Curiouser and curiouser. The ethernetworked host that runs lpd and a laserjet w/o trouble is down today. Strange that it should work so easily, given these troubles. Is the token ring doing something strange? I remember some discussion of lpd here in recent weeks. Anybody wanna repost a summary? Sounds like a subject for the FAQ file, too. > >> Question: Does anyone have a solution? > >Sacrifice a virgin. Say the magic words "A la peanut butter >sandwich." Get a bigger hammer. > Time to find a REALLY big hammer... > Eric Bushnell UW Civil Engr etb@zeus.ce.washington.edu