home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!agate!dog.ee.lbl.gov!network.ucsd.edu!sdcc12!xm9
- From: xm9@sdcc12.ucsd.edu (richard g. adair)
- Newsgroups: comp.sys.hp
- Subject: Re: HP remote print server SYSV like or BSD like ?
- Summary: remote printing
- Keywords: remote printing
- Message-ID: <36064@sdcc12.ucsd.edu>
- Date: 24 Jul 92 01:37:10 GMT
- References: <c8dm=4n@dixie.com> <1992Jul22.163014.16577@eye.com>
- Sender: news@sdcc12.ucsd.edu
- Organization: Arete Associates, San Diego
- Lines: 21
- Nntp-Posting-Host: sdcc12.ucsd.edu
-
- In article <1992Jul22.163014.16577@eye.com> paul@eye.com (Paul B. Booth) writes:
- >In article <c8dm=4n@dixie.com> stan@dixie.com (Stan Brown) writes:
- >>
- >> Is the HP remote print *server* SYSV like or BSD like?
- >
- >The hp-ux print spooler system is SYSV (lp, lpadmin, and lpsched are SYSV),
-
- If you really only have a SYSV spooler on your machine, try using my
- favorite command "on". You can issue the command:
-
- on remotemachine lp filename
-
- The "on" command will keep your current directory when issuing the
- remote command, and even NFS mount the directory if necessary.
- This is gross, but it works just dandy. (This is also how you get
- around buying lots of FORTRAN compiler licenses: make one machine a
- compiler server and all the rest alias f77 to "on machine f77 $*"
-
- Tony Burzio
- Arete Associates
- San Diego, CA
-