Re: Is lpr outdated, unsupported?, ie. lpr or lp?
From: Greg Andrews (gerg_at_panix.com)
Date: 05/14/03
- Next message: Greg Andrews: "Re: Solaris Kernel job opportunity"
- Previous message: Dave Uhring: "Re: Solaris Kernel job opportunity"
- In reply to: Jon: "Re: Is lpr outdated, unsupported?, ie. lpr or lp?"
- Next in thread: Michael Vilain
: "Re: Is lpr outdated, unsupported?, ie. lpr or lp?" - Reply:(deleted message) Michael Vilain
: "Re: Is lpr outdated, unsupported?, ie. lpr or lp?" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 14 May 2003 05:33:44 +0000 (UTC)
By the way, Jon, it's not necessary to quote my entire article
(which was long) in order to post the reply you wrote. Just a
few lines would have been sufficient.
jon@nytimes.com (Jon) writes:
>
>The main issue right now is whether to use a Solaris print server OR
>an HP print server for sending to the HP network printers.
>
By "HP print server", I assume you mean "computer running HP/UX"
(HP's flavor of Unix), and not "HP Jetdirect box".
>
>I don't quite understand the HP JetDirect print server. Does it work
>totally independent of any Solaris print server, of does it work with
>a Solaris print server?
>
Which of the three things named "Jetdirect" and made by HP are you
asking about? The network card that installs into printers like
the Laserjet series is named "Jetdirect". The standalone box with
a network interface and 1-3 printer ports is also named "Jetdirect".
Both of these do indeed operate independently of any Solaris server,
since they don't run on Solaris.
However, you probably are asking about the product I mentioned in
my post, the "HP Jetdirect software for Solaris". The HP software
acts as a text-mode front end for creating the printer queues, and
as the print system's back end for delivering print jobs to HP network
printers.
To be more specific, the Solaris print system is invoked by the user
(the lp or lpr command), places the print file into the queue, and
then the Solaris lpsched daemon invokes the interface program for the
printer so it can deliver the print file to the printer. The interface
program is where control passes to the Jetdirect software's "back end."
The interface program (a shell script) was installed by the Jetdirect
software. It makes a network connection to the printer, sends any init
commands, and feeds the print file to the printer. Then the interface
exits with a success/fail code (and perhaps an error message). Control
returns to the Solaris lpsched, which deletes the print file from the
printer queue. Or, if there was an error, sends e-mail to the user
who submitted the print file.
>
>Also, I don't see any administration manuals on the hp.com web site
>for JetDirect print servers. I see the software download area, but
>without docs it's a bit difficult to learn. If anyone knows where
>they are located I'd appreciate it. Also, I'm concerned about
>support. Sun Support would help with Solaris print server, but
>probably not if I run into problems with an HP print server.
>
See this post for URLs to some of the docs HP has on their website
about their Jetdirect software:
http://groups.google.com/groups?as_umsgid=b5t61l%2490q%241%40reader2.panix.com
Sun Support knows a lot about the Jetdirect software, but it's true
that if you run into a problem that is narrowed down to just the
Jetdirect software, Sun Support won't be able to help much.
But that was one of two options I mentioned. The other was to use
the Solaris netstandard interface to deliver the print jobs to the
network printers (and use a FIFO queue instead of free-for-all
connections). The netstandard interface has far less functionality
when compared to the Jetdirect software. It can only transport the
files to the printer. No fancy init commands to select the printer's
fun features. However, it's supported by Sun Support.
>
>lpstat -v labprinter
>system for labprinter: labprinter
>
Yes, for that printer you have Solaris congfigured in the "remote
printer" mode, as I described in my previous post.
As for delivering files to another computer for further processing
before they're sent to the printer, it depends on what that "further
processing" is. Some people have used the print system to transfer
files (and used the interface to perform the processing). If you're
going to try FTP, then consider using UUCP instead. UUCP is old and
arcane, but for the purposes of transferring files to another computer
and automatically running programs after the files are delivered,
then UUCP runs rings around FTP. The command is configurable, and
it's not invoked until the file is transferred successfully. You can
have status returned to you automatically, and security is built in.
Just a suggestion.
-Greg
-- Do NOT reply via e-mail. Reply in the newsgroup.
- Next message: Greg Andrews: "Re: Solaris Kernel job opportunity"
- Previous message: Dave Uhring: "Re: Solaris Kernel job opportunity"
- In reply to: Jon: "Re: Is lpr outdated, unsupported?, ie. lpr or lp?"
- Next in thread: Michael Vilain
: "Re: Is lpr outdated, unsupported?, ie. lpr or lp?" - Reply:(deleted message) Michael Vilain
: "Re: Is lpr outdated, unsupported?, ie. lpr or lp?" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
