Thread View: comp.protocols.appletalk
2 messages
2 total messages
Started by Craig Morgenstern
Mon, 11 Jan 1993 15:56
papif/lpd prob running cap60.126 w/ SUN NIT (HELP!)
Author: Craig Morgenstern
Date: Mon, 11 Jan 1993 15:56
Date: Mon, 11 Jan 1993 15:56
45 lines
1971 bytes
1971 bytes
We've just switched from IPtalk via a kbox to native ethertalk (phase 2) on
a SUN3 (4.0.3) and a SPARCstation-2 (4.1.1), and now laserwriter access is
broken on both machines. In lpd-errs, we get the following message
Jan 11 09:14:39 red lpd[3238]: restarting lw132
Jan 11 09:15:29 red last message repeated 59 times
Here's the printcap entry, cap.printers entry, and the shell script to
invoke papif (these worked when we were using IPtalk):
(printcap)
lw132:\
:lp=/dev/lw132:\
:sd=/var/spool/lw132:\
:sf:\
:lf=/var/adm/lw-log:\
:if=/usr/local/lib/cap/lw132:\
:of=/usr/local/lib/cap/papof:
(cap.printers)
lw132=132 PLW:LaserWriter@CoSc Labs
(lw132 shell script)
#!/bin/sh
BANNERLAST=0
BANNERFIRST=0
DOACCT=0
export BANNERLAST BANNERFIRST DOACCT
/usr/local/lib/cap/papif -P lw132 $*
Aufs, atlook, etc all work fine, and we can print a postscript file to lw132
using lwpr. Under ethertalk, the machines are in a different zone than
they were when running IPtalk. etcdest and all other dests were all set to
/usr/local/lib/cap.
I've RTFM all weekend, and I'm completely stymied. I haven't been following
threads about printer probs, so I don't know if this is a common prob or not.
Could someone in the know please enlighten me? Any suggestions would be
very much appreciated!
Thanks in advance.
Craig Morgenstern
morgenst@riogrande.cs.tcu.edu
Re: papif/lpd prob running cap60.126 w/ SUN NIT (HELP!)
Author: Paulo Antonio Costa Goncalves
Date: Tue, 12 Jan 1993 12:44
Date: Tue, 12 Jan 1993 12:44
69 lines
3097 bytes
3097 bytes
In article <1993Jan11.155625.18505@riogrande.cs.tcu.edu> Craig Morgenstern,
morgenst@riogrande.cs.tcu.edu writes:
>We've just switched from IPtalk via a kbox to native ethertalk (phase 2) on
>a SUN3 (4.0.3) and a SPARCstation-2 (4.1.1), and now laserwriter access is
>broken on both machines. In lpd-errs, we get the following message
>
> Jan 11 09:14:39 red lpd[3238]: restarting lw132
> Jan 11 09:15:29 red last message repeated 59 times
>
>
>Here's the printcap entry, cap.printers entry, and the shell script to
>invoke papif (these worked when we were using IPtalk):
>
> (printcap)
> lw132:\
> :lp=/dev/lw132:\
> :sd=/var/spool/lw132:\
> :sf:\
> :lf=/var/adm/lw-log:\
> :if=/usr/local/lib/cap/lw132:\
> :of=/usr/local/lib/cap/papof:
>
> (cap.printers)
> lw132=132 PLW:LaserWriter@CoSc Labs
>
> (lw132 shell script)
> #!/bin/sh
> BANNERLAST=0
> BANNERFIRST=0
> DOACCT=0
> export BANNERLAST BANNERFIRST DOACCT
> /usr/local/lib/cap/papif -P lw132 $*
>
>Aufs, atlook, etc all work fine, and we can print a postscript file to lw132
>using lwpr. Under ethertalk, the machines are in a different zone than
>they were when running IPtalk. etcdest and all other dests were all set to
>/usr/local/lib/cap.
>
>I've RTFM all weekend, and I'm completely stymied. I haven't been following
>threads about printer probs, so I don't know if this is a common prob or not.
>Could someone in the know please enlighten me? Any suggestions would be
>very much appreciated!
>
>Thanks in advance.
>
>Craig Morgenstern
>morgenst@riogrande.cs.tcu.edu
What is the protection of /dev/nit in your SUNs?
I had to "chmod 660 /dev/nit", "chgrp staff papif" and "chmod g+s papif" (set
gid bit
to staff). Then it all worked!
Hope this helps!
Paulo Goncalves.
****************************************************************************
***
Paulo Antonio Costa Goncalves E-mail: pacg@inesc.pt
INESC - CCAE Eunet: mcsun!inesc!pacg
Tel. 351-1-3100069 mcsun!inesc!pacg@uunet.UU.NET
Lisboa - PORTUGAL PSI/VMS: PSI%(+0268)004010314::inesc::pacg
****************************************************************************
***
The Golden Rule is: Who has the Gold, Makes the Rule !!!
****************************************************************************
***
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads