home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.sysv386:16268 comp.unix.sys5.r4:441
- Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!eff!iWarp.intel.com|ichips!hfglobe!ptdca2!snelson
- From: snelson@ptdca2.intel.com (Shannon Nelson)
- Subject: Need help on remote printing sVr4 to sVr4
- Message-ID: <Bx9r79.7Io@hfglobe.intel.com>
- Originator: snelson@ptdca2
- Sender: news@hfglobe.intel.com (News User)
- Nntp-Posting-Host: ptdca2.intel.com
- Organization: Portland Technology Development, Intel Corp., Aloha, OR
- Distribution: usa
- Date: Fri, 6 Nov 1992 00:40:21 GMT
- Lines: 59
-
- Alright, I give up. How do I get my Esix sVr4.0.4 boxes to send
- printer requests to the one central Esix server that has the printer?
-
- More specifically: I have several Esix sVr4.0.4 boxes, all on the
- network. One (ptdca0) is a fileserver with an HP Laserjet II with a
- postscript cartridge. There are several others on the net that I
- want to have set up so that lp requests get forwarded to the server.
- I think I've followed the directions (if that's what you'd call them)
- correctly, but it still doesn't work from the remote systems.
-
- The server's printer is set up with the following configuration file:
- Banner: on
- Content types: PS
- Device: /dev/tty00
- Fault: beginning
- Interface: /usr/lib/lp/model/PS
- Printer type: PS
- Modules: default
- The /etc/lp/Systems file has the line
- ptdca2:x:-:s5:-:n:10:-:-:no comment, please
- The lpstat -t output says
- scheduler is running
- system default destination: laser
- members of class postscript:
- laser
- postscript accepting requests since Thu Oct 15 12:58:34 PDT 1992
- laser accepting requests since Thu Oct 15 13:21:54 PDT 1992
- printer laser is idle. enabled since Thu Oct 15 13:22:21 PDT 1992. available.
- character set
-
- This printer works wonderfully for anything printed from an lp command
- on the server: ASCII, troff, and postscript.
-
- On the remote system (ptdca2), the configuration file looks like
- Content types: PS
- Printer type: PS
- Remote: ptdca0!laser
- with an /etc/lp/System entry of
- ptdca0:x:-:s5:-:n:10:-:-:Fileserver's printer
- The lpstat -t output is
- scheduler is running
- system default destination: laser
- system for laser: ptdca0 (as printer laser)
- laser accepting requests since Thu Oct 15 20:28:56 GMT 1992
- printer laser is idle. enabled since Thu Oct 15 20:29:06 GMT 1992. available.
- character set
- any-2 snelson 15165 Oct 15 20:52
-
- Both systems have the lpNet process running. Normal network connections
- are fine (rlogin, telnet, rcp, nfs, ...). When I submit an lp request to
- the remote system, the request is queued up and sits there forever.
-
- What am I missing? What else do I need to check? Help me, Mr Wizard!
-
- --
- ==============================================================================
- Shannon Nelson Portland Technology Development, Intel Corp.
- snelson@ptd.intel.com (503) 642-8149 I don't speak for Intel
- Parents can't afford to be squeemish.
-