[comp.sys.apollo] BSD lpd

herb@blender.uucp (Herb Peyerl) (02/10/91)

obrennan@CC3.CC.UMR.EDU (obrennan) writes:
>	Although lpd starts up fine, the jobs just get queued up
>	and don't move.  An "lpq -Pxx" gives "Warning: no daemon present"
>	and an "lpc restart xx" gives "no daemon to abort, starting daemon"
>	But the daemon is there....
>	
>Do you have LLBD running?                             

I don't see what llbd has to do with it.  Unix lpd stuff isn't
NCS based as far I as I'm aware. 

I've been playing around with the berkeley print stuff the last
couple of weeks and haven't had any problems with it at all.  I
did however experience the "No Daemon present" syndrome and in
fact, haven't been able to get that to go away.  It doesn't seem
to affect the operation of the lpd stuff though.  What does your
printcap entry look like for this printer?  If you set up this
printer to work from one of your Sparc's does it work? (I'm
wondering if its a problem with your /dev/printer socket or 
whether the problem is deeper.  Also, how 'bout setting up your
device to be /dev/tty01 instead of /dev/sio1.   I'm not overly
aware of what exactly the differences are but I've found in the
past that Unix utilities much prefer the ttyxx stuff over the
sio stuff. 

Incidentally, we much prefer the NCS printing stuff to lpd
but that's not the point. 
-- 
--------------------------------------------------------------------------
UUCP: herb@blender.UUCP   || #define Janitor Administrator
ICBM: 51 03 N / 114 03 W  || Apollo System_Janitor, Novatel Communications
"I spilled spot remover on my dog and now he's gone..." <Steven Wright>

fridman@cpsc.ucalgary.ca (fridman) (02/14/91)

I'm trying to get the BSD printing to run.  

Although lpd starts up fine, the jobs just get queued up
and don't move.  An "lpq -Pxx" gives "Warning: no daemon present"
and an "lpc restart xx" gives "no daemon to abort, starting daemon"

But the daemon is there....

All the modes on the files are just what the manual said, and the 
printer is hooked up because I can just dump stuff to it through
"cat zzz > /dev/sio1" and it comes out fine.

I've tried to kill and restart lpd, remove the /dev/printer socket,
remove the lock files in /usr/spool/lpd/xx...

I also have entries for the printer host in /etc/hosts.equiv, 
/etc/hosts.lpd and /usr/spool/lpd/servername.

All this is done from the node to which the printer is attached..

NOTE:  I am doing nothing with the aegis printing system, although
       I did get a suggestion to get aegis printing up first and then
       place BSD printing on top.  I don't see why BSD printing won't work:{

Anybody had similar experiences???

	RF.

rees@pisa.ifs.umich.edu (Jim Rees) (02/21/91)

In article <1991Feb10.094421.i@>, herb@blender.uucp (Herb Peyerl) writes:

  I don't see what llbd has to do with it.  Unix lpd stuff isn't
  NCS based as far I as I'm aware. 

Then I wonder what lb_$register is doing in its symbol table?

I couldn't get lpr/lpd to work either.  My solution was to grab the Berkeley
sources and compile them myself.  Works fine now.

ianh@bhpmrl.oz.au (Ian Hoyle) (02/22/91)

rees@pisa.ifs.umich.edu (Jim Rees) writes:

>In article <1991Feb10.094421.i@>, herb@blender.uucp (Herb Peyerl) writes:

>  I don't see what llbd has to do with it.  Unix lpd stuff isn't
>  NCS based as far I as I'm aware. 

>Then I wonder what lb_$register is doing in its symbol table?

>I couldn't get lpr/lpd to work either.  My solution was to grab the Berkeley
>sources and compile them myself.  Works fine now.

We have been using lpr/lpd since sr10.0 (do we all remember *that* release :-).
Not without problems tho' ... we could never get it running with just lpd on a
'server' node. We have always found that we need to have lpd running on
each node. No big deal. Remote printing to other hosts running lpd such as
VAXen and now even SGI machines works fine.

	ian
--
                Ian Hoyle
     /\/\       Image Processing & Data Analysis Group
    / / /\      BHP Research - Melbourne Laboratories
   / / /  \     245 Wellington Rd, Mulgrave, 3170
  / / / /\ \    AUSTRALIA
  \ \/ / / /
   \  / / /     Phone   :  +61-3-560-7066
    \/\/\/      FAX     :  +61-3-561-6709
                E-mail  :  ianh@bhpmrl.oz.au

system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) (03/20/91)

In article <9103082016.AA01167@cc2.cc.umr.edu> obrennan@CC3.CC.UMR.EDU (obrennan) writes:
>	I'm trying to hook up a printer to one of the serial lines on
>	a DN4500  running SR10.3.
>---------------------------------------------------------
>In the printcap file you can use XC and XS to clear and set 
>the LOCAL MODE bits, and FC and FS to clear and set the SG_FLAGS
>as documented in the MAN pages section 4 for TTY. These flag
>bits control the tty interface. The ^Q/^S control mode (same as
>-insynch) is set by the LOCAL MODE bits. 

To be more specific, here are the settings I have been using in
/etc/printcap for over a year to connect an Imagen laser printer to a DN10000:

imagen:\
	:lp=/dev/tty03:\
	:af=/usr/adm/imagen_acct/imagen:\
	:lf=/usr/spool/lpd/imagen/log:\
	:sd=/usr/spool/lpd/imagen:\
	:lo=lock:\
	:br#19200:\
	:fc#0177777:\
	:xc#0177777:\
	:fs#0340:\
	:xs#044040:\
	:rw:\
	:sh:\
	:mx#10000:\
	:cf=/usr/local/lib/icif:\
	:df=/usr/local/lib/idvi:\
	:gf=/usr/local/lib/igraph:\
	:if=/usr/local/lib/ipf:\
	:nf=/usr/local/lib/idimp:\
	:rf=/usr/local/lib/ifort:\
	:tf=/usr/local/lib/icat:\
	:vf=/usr/local/lib/imp:\
	:rs:

These settings are for 8 bit, no parity, 19200 baud, XON/XOFF flow
control, no character translations ("raw" mode), no echo.
Note that the various filters are part of the Imagen UNIX Software.

The difference between /dev/siox and /dev/tty0x is mainly in the way the
cable must be wired -- if you are going to use the tty0x devices,
you must make sure DCD is wired high (or held high by the printer).
The siox devices don't care about DCD. (I am not 100% sure that it is
DCD, since I don't have my printer cable wiring diagram here, but it is
one of the control pins for sure -- I'm pretty sure it is DCD since this
causes trouble when you want to talk to a modem: it won't raise DCD
until it gets a connection, but you can't get a connection until you can talk
to the modem).

Mike.
-- 
Mike Peterson, System Administrator, U/Toronto Department of Chemistry
E-mail: system@alchemy.chem.utoronto.ca
Tel: (416) 978-7094                  Fax: (416) 978-8775