Hi Norm. Thanks for the info. I did check out the /var/spool/lp/tmp direcory and the permissions were as follows:
drwxrwxr-x 2 lp lp .... So both the user and group 'lp' could read/write/execute to the directory. I have a sneaking suspicion that it could be the PPD driver that's causing the problems so will now try NOT using the PPDs and going back to the faithfull old version of printing. Regards, Jeff Turner Norm wrote... > For the cost of a large Lou Malnati's pizza > (http://www.loumalnatis.com/), you can purchase a printing license that > entitles you to print more than one print job. ;-) > > Seriously though, It's not clear to me exactly what's going on here. > The message appears to come from the netstandard interface script. What > are your permissions on /tmp ? netstandard creates a file > /tmp/$(uname -n).$$ during execution that it ends up sending out to the > printer. The problems that you > are seeing are related to creating this file. It's likely to be either > a permission problem or the filter failing to execute cleanly, but there > are other possibilities. > > If you turn on "lpr.debug" in the syslog(1m), attempt to print a job, > and send a copy of the syslog output and your queue configuration from > /etc/lp, either I or someone else on this list can probably take a look. > > -Norm > PS. > FWIW, I installed a queue on my desktop system for my HPLJ4650 using > the LJ4300 ppd file and was able to print to it. I'm running Nevada > build 57, but the relevant bits should be pretty much identical. > Trusted bits should have no impact on this. > > Jeff turner wrote: >> I tried to install an HP LaserJet 4350 network printer using the PPD >> files. The nearest printer driver I assumed could be used was the HP >> LaserJet 4300 type (although I did try with other types to see if they >> would work). >> >> The strange thing that happened was that root could print to the printer >> once and once only. Subsequent attempts to print to the printer, either >> by root or a normal user, were met with "notifying user" messages in the >> lpstat -[t|o] output then a cancellation of the print job and an email >> message from the lp daemon stating that the print job had been aborted >> because it could not read 'the temporary file ""'. >> >> I did not install the Trusted Extensions packages but think that this >> problem may be related in some way to an in-built security control. >> >> I checked file ownerships and permissions and all of the appropriate >> directories in /var/spool/lp and /etc/lp were owned by user and group >> 'lp'. >> >> Any help would be greatly appreciated. >> >> Thanks, >> Jeff Turner (aka jifftuna) >> >> >
