tperala@UB.D.UMN.EDU (Tim Perala) (06/09/89)
I tried to post this earlier, but I'm afraid some other nonsense was broadcast in its stead. Here, we'll try again... We are running Umax 4.2 R3.3.0, NFS R1.2. We are booting a Sun 3/50 and Sun 4/110 both running SunOS 4.0 from our Encore. This all seems to be working fine, except for lpd/lpr on the client Suns. When either Sun boots and lpd is started, any jobs pending in the print queues are flushed to the proper remote machines for printing, but after the initial queue flushing, lpd/lpr/lpc all seem to mis- behave. Lpd does run in the background properly, but I get the following behaviour when trying to manipulate the queue... =================================================================== wiffy27: lpq no entries wiffy28: lpr .login lpr: connect: Socket operation on non-socket jobs queued, but cannot start daemon. wiffy29: lpq no entries wiffy: Warning: no daemon present Rank Owner Job Files Total Size 1st tperala 15 .login 787 bytes wiffy30: /usr/etc/lpc restart 1 1: no daemon to abort 1: /usr/etc/lpc: connect: Socket operation on non-socket couldn't start daemon =============================================================== The printcap entry looks correct... 1|mwah|MWAH|m1|lp|PostScript|postscript|MWAH 143 printer:\ :lp=:rp=mwah:rm=ub.d.umn.edu:sd=/usr/spool/lpd:\ :lf=/usr/adm/lpderrs:mx#0: Since lpd (and company) use UNIX domain sockets (at least in Sun's implementation), I suspect that that is the problem. To my knowledge UNIX domain sockets have NEVER worked under UMAX. Is my suspicion correct about the UNIX sockets? What else could be causing this? The exact same behaviour both Sun clients. If it is the UNIX domain sockets under UMAX, how do I fix this? Any help is appreciated. -- Tim Perala Systems Programmer Information Services University of Minnesota, Duluth (218) 726-6122
jdh@bu-cs.BU.EDU (Jason Heirtzler) (06/09/89)
I just noticed this myself when I set up a Sun workstation to boot
off one of our Encores. The problem is a bug in Encore's NFS and they
claim that the following patch fixes it (we haven't tried it yet)
# adb -w /Umax.image
iftont_tab+18?W6
^D
You will need to reboot for the fix to take effect. Be sure to make
a backup copy of /Umax.image before you do this.
Let me know if it works..
Jason Heirtzler
jdh@bu-it.bu.edu