carroll@bcsaic.UUCP (Jeff Carroll) (07/27/90)
I am getting a mystifying error (mystifying because there's nothing in the docs about it) from WIN/TCP on my uVAX II. %LPDSMB-F-FILEREAD, What is happening? What should I check? Jeff Carroll carroll@atc.boeing.com
lars@spectrum.CMC.COM (Lars Poulsen) (07/31/90)
In article <28900@bcsaic.UUCP> carroll@bcsaic.UUCP (Jeff Carroll) writes: >I am getting a mystifying error (mystifying because there's nothing in >the docs about it) from WIN/TCP on my uVAX II. > >%LPDSMB-F-FILEREAD, > >What is happening? What should I check? Decoding the message identifier according to normal rules says that a component called LPDSMB (probably a print symbiont which is a client for the Berkeley Line Printer Daemon; i.e. talking to a remote print queue over the network) had a FILEREAD error. Sounds to me like (1) You have a print queue connected to a printer on another system (2) A file was submitted to this print spooler, and probably deleted while it was sitting in the queue (was the print server down for quite a while ?) I would expect that you are getting this message on the console. Does it say which file it had trouble reading ? Is the file really gone ? Does it say what kind of error it got when trying to read it ? -- / Lars Poulsen, SMTS Software Engineer CMC Rockwell lars@CMC.COM
imp@dancer.Solbourne.COM (Warner Losh) (08/01/90)
My original reply to this bounced today, so I'll post instead: In article <28900@bcsaic.UUCP> carroll@bcsaic.UUCP (Jeff Carroll) writes: >I am getting a mystifying error (mystifying because there's nothing in >the docs about it) from WIN/TCP on my uVAX II. >%LPDSMB-F-FILEREAD, >What is happening? What should I check? This is telling you that your lpd deamon can't read some file. A short chat with the author of lpr/lpd for win/tcp reveals that this error is usually caused by the spool directory having the wrong protections. These directories should be readable and writable by the [LPD] account, but no other accounts (to avoid security holes) should be able to write to these directories. See the appendix of the System Admin guide for more details. In article <1990Jul30.203106.22496@spectrum.CMC.COM> lars@spectrum.CMC.COM (Lars Poulsen) writes: >Decoding the message identifier according to normal rules says that >a component called LPDSMB (probably a print symbiont which is a client >for the Berkeley Line Printer Daemon; i.e. talking to a remote print >queue over the network) had a FILEREAD error. Yes, it is a LPR/LPD protocol speaker for VMS. LPD.EXE (the part of the system that worries about talking lpr/lpd to neighbors) runs effectively as SYSTEM. It can put files into the queue with no problems. However LPDSMB runs as LPD so there can be a few protection problems if the both the ownership of the spool directory (specified with the /SPOOL_DIR=xxxx qualifier in the TWG$TCP:[NETDIST.ETC]PRINTCAP file) isn't [LPD]. When setting the ownership of a spool directory that may have files in it, you will want to also set the ownerships of the files in that directory as well. Warner -- Warner Losh imp@Solbourne.COM