[comp.sys.hp] yp & remote printing

kelso@gwusun.gwu.edu (John Kelso) (09/08/89)

I have discovered what I hope is not a "feature" of remote printing
on HP 9000's.  I apologize for the long-winded description.

Here is our setup:

Sparko is an 835-SE, with a serial printer.  It is a yellow pages
client of domain gwyp.  It is using netgroups; it's /etc/hosts.equiv
file has the single line "+@all".  the all netgroup has entries that
say (sparko,,gwyp) (peabody,,gwyp), among others.

Peabody is a 370 that wants to print using sparko's printer.  It is
also a yellow pages client of domain gwyp, uses netgroups, and has a
/etc/hosts.equiv file with the single line "+@all".

The yp master is a Sun.  It's /etc/hosts.equiv also is the single line
"+@all". It has a printer that both sparko and peabody can use
remotely.

Here's the problem:

When I print a file on peabody that should go to sparko's printer, and
then issue a lpstat -t command, I see, among other things:

printer hp7580 now sending hp7580-4 to sparko.
printer queue for hp7580
peabody: waiting for sparko to come up

If I go and edit sparko's /etc/hosts.equiv file to include the line
"peabody", and issue another print command, everything goes across
correctly.

This seems to tell me that the remote printer software on the HP
doesn't know about yp netgroups. (Other commands, such as rlogin, seem
to understand netgroup.)

Any comments or advice?  Many thanks in advance.

John
-- 
      John Kelso, System Engineer, George Washington University
     SEAS Computing Facility, 725 23rd St NW, Washington DC 20052
	    kelso@gwusun.gwu.edu  -or-  uunet!gwusun!kelso
--

burzio@mmlai.UUCP (Anthony Burzio) (09/10/89)

In article <1468@bleen.gwusun.gwu.edu>, kelso@gwusun.gwu.edu (John Kelso) writes:
> When I print a file on peabody that should go to sparko's printer, and
> then issue a lpstat -t command, I see, among other things:
> 
> printer hp7580 now sending hp7580-4 to sparko.
> printer queue for hp7580
> peabody: waiting for sparko to come up
> 

It's not the hosts.equiv table, because that would give access
violations.  I ran into this problem last week and traced it to
inetd not working correctly.  According to the manual on rlpdaemon,
inetd can start remote printer jobs with the entry:

printer stream tcp nowait root /usr/lib/rlpdaemon rlpdaemon -i

This doesn't work, and gave me the same error in a similarly configured
system.  Put the command /usr/lib/rlpdaemon in your rc file and it'll
work just great (you will see  [rlpdaemon] listed in a ps -ef).  The
line to start lpdaemon goes at the end ofthe localrc() function.
For clusters, since rc is NOT a context dependent file, you need to do
something like:

        # Start remote printer daemon.
        if [ "`uname -n`" = sparko ]
        then    
                echo "Starting remote printer daemon."
                /usr/lib/rlpdaemon
        else
                echo "No remote printing"
        fi

in order to stop discless nodes from starting the rlp daemon.  Hope
this helps...

*********************************************************************
Tony Burzio               * I need more Dr. Who episodes!
Martin Marietta Labs      *
mmlai!burzio@uunet.uu.net *
*********************************************************************