I asked:
> I just upgraded one of our machines from 2.3 to 2.4. My problem is
> that printing to that system from other machines has stopped.
It turns out that I needed to spend more time Reading The Fine
Answerbook. Page 329 of the administrator's handbook ("How to Set Up
a SunOS 5.x Print Server") listed a number of steps you have to take
to tell the printer system to listen for requests from the network.
Apparently in setting up previous printers I had used the
admintool/printer manager window interface, which does that invisibly.
This time I tried adding it with the lpadmin command, which doesn't.
The steps involved are ugly enough that it's probably better to use
the printer manager interface. If you have to do special things for your
printer (as I did), it's probably best to create a printer with the
GUI, delete it, and then run your script.
What got me on the right track was discovering a mention of the
nlscommand somewhere in the documentation, and then noticing that
"/usr/sbin/nlsadmin -v tcp" got me an error message on ozma but a list
of things listening on machines with working printer servers.
Thanks to Linda Cygan (cygan@wpm.com), who suggested that I needed to
use the BSD option to install the printer. Sun is changing back to
BSD-based internals in the future, and in fact the Printer Manager
complains if you set the system type to System V. This suggestion
helped get me on the right track; I was rea
The full query follows.
-----------------------------------cut here-----------------------------------
I just upgraded one of our machines from 2.3 to 2.4. (I used the
Sunsoft version, not the Sunmicro one.) My problem is that printing
to that system from other machines has stopped. When I try to print
something, I get this output:
tc-alnilam# lpstat -o hp4b
hp4b-202 root 40613 Jan 10 12:56
tc-alnilam# /usr/ucb/lpq -Php4b
system not responding
Rank Owner Job Files Total Size
active root 202 color_test.ps 40613 bytes
tc-alnilam#
What I don't understand is why remote printing broke, but printing on
ozma (the machine to which hp4b is attached) works.
tc-ozma# lpr -Php4b ~ted/Admin/color_test.ps
tc-ozma# lpq !!:1
lpq -Php4b
hp4b is ready and printing
Rank Owner Job Files Total Size
active root 20 color_test.ps 40613 bytes
This seems to happen with and without the jumbo lp patch (101959-02)
installed.
The log file on remote machines looks like this:
# for a 2.4 machine:
01/10 12:47:25 c 11657 ozma connection failed
01/10 12:47:27 p 11656 <none> Started child for ozma, pid = 11701
01/10 12:47:29 c 11701 ozma lpd retrying (1) connection to ozma in 30 secs
01/10 12:47:59 c 11701 ozma lpd retrying (2) connection to ozma in 60 secs
01/10 12:48:59 c 11701 ozma lpd retrying (3) connection to ozma in 120 secs
01/10 12:51:00 c 11701 ozma lpd retrying (4) connection to ozma in 240 secs
01/10 12:55:00 c 11701 ozma lpd retrying (5) connection to ozma in 480 secs
# for a 2.3 machine:
01/10/95 12:34 p 188 <none> Started child for ozma, pid = 25146
01/10/95 12:34 c 25146 ozma Starting.
01/10/95 12:34 c 25146 ozma Could not connect to remote child.
01/10/95 12:46 c 25146 ozma Could not connect to remote child.
01/10/95 12:56 c 25146 ozma Could not connect to remote child.
Did Sun blow this one, or am I missing something obvious?
-----------------------------------cut here-----------------------------------
Ted Rodriguez-Bell
Experimental Astrophysics Group
Space Sciences Lab, UC Berkeley
ted@ssl.berkeley.edu
(510)-643-6214
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:14 CDT