🚀 go-pugleaf

In article <1991Apr15.193742.8575@dg-rtp.dg.com> knightp@liberty.rtp.dg.com (Philip Knight) writes:
|I'm on a V.4 system and am attempting to add the lp service to the listen(1M)
|port monitor via the pmadm(1M) command.  Page 9-14 of the V.4 System
|Administrator's Guide gives the following syntax:
|
|   pmadm -a -p tcp -s lp -i root -V `nlsadmin -V` \
|   -m `nlsadmin -o /var/spool/lp/fifos/listenS5`
|
|I get no errors when I execute this command and pmadm -l indicates that the
|service has been added successfully.  What I don't understand, however, is
|why there is no private address (provided via -A option of the nlsadmin
|command) associated with the service.  Does listen moditor a default address
|if neither a private address nor dynamic addressing (via the -D option to
|nlsadmin) is specified?  Is this an error in the documentation?

No, no error, there is no address for the lp service.  The address
used is that of the listener service.  The remote system asks the
listener for a connection to the lp service.  The listener has a "well
know address" that other systems will use to connect to the local
system, then request a local service; in this case lp.

If you look a little further in the SAG, you'll see the entry for
accepting connections from systems using the lpr/lpd service.  Lpd
expects to connect to a specific address, so the -A option is used to
provide the address that lpd wants.

DavidM
davidm@commodore.cbm.com