home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.att
- Path: sparky!uunet!wupost!uwm.edu!psuvax1!guardian.cs.psu.edu!leung
- From: leung@guardian.cs.psu.edu (Kin Ki Leung)
- Subject: using uucp to do remote printing
- Message-ID: <Bs5twC.64q@cs.psu.edu>
- Sender: news@cs.psu.edu (Usenet)
- Nntp-Posting-Host: guardian.cs.psu.edu
- Organization: Penn State Computer Science
- Date: Wed, 29 Jul 1992 17:00:11 GMT
- Lines: 25
-
- The following is posted for a friend.
-
- --
-
- I use direct line to connect an AT&T Starserver running System V 4.0.2
- to a Sun server running 4.1.2, and set up uucp between the two systems.
- Then I used lpadmin to set up printing from the Starserver to the
- Sun system (ie the printer is connected to the Sun), I am able
- to print from the Starserver, however, lpstat -t on the Starserver
- still showed the jobs on the print queue even long after the jobs
- were printed. What I could have done so that jobs were removed
- from the queue after it was printed?
-
-
- A second question: I have two Starservers, and I can set up uucp over
- tcp/ip on the Starservers. With one of the Starservers (say A) directly
- connected to a Sun server, I believed I should be able to set
- up printing from the second Starserver (say B) to the printer connected to the
- Sun server without setting up another direct line, but on
- Starserver B using lpadmin -p printername -s serverA!printer
- does not seem to work, am I missing something ?
-
- thanx
-
- Ann
-