Topic: printer problem with v4b5

[sasha]

I have just upgraded the rpms to beta5 and installed LPRng at a site.
The printer worked perfectly with b3 and lpr.

Now the printer does not print at all from windows workstations.
The job goes into the queue and then disappears. No output.
There is nothing in messages.

Here is a screen-dump of trying to print at the console:

lpr /home/e-smith/configuration
Status Information:
 sending job 'root@penguin+830' to epson@localhost
 connecting to 'localhost', attempt 1
 connected to 'localhost'
 requesting printer epson@localhost
 sending control file 'cfA830penguin.projdev.co.za' to epson@localhost
 error 'LINK_TRANSFER_FAIL' sending file 'cfA830penguin.projdev.co.za' to epson@
localhost
 job 'root@penguin+830' transfer to epson@localhost failed

Tried reverting back to lpr, but then it just prints garbage!

Is there still a problem with the setting of the folder rights ?

[sasha]

I did manage to get the printer to print from the console by playing around with
chmod 0700 /var/spool/lpd/* and chmod 0700/var/spool/*

Samba jobs still do not going through. The jobs are all sitting in the /var/samba directory and are not being serviced.

Owner and group on the /var/samba directory is root root. And permissions
are rwxrwxrwt

[Joseph Morrison]

Hello Sasha,

> I have just upgraded the rpms to beta5 and installed LPRng at a
> site. The printer worked perfectly with b3 and lpr.

Sounds like a permissions/ownership problem due to the manual upgrade. Try deleting and re-creating the printer from the user interface; that will guarantee that the queue has the right permissions and ownership.

Good luck!
- Joe

[sasha]

The fix posted by George Steidley on devinfo resolved the problem.

TO recap : Just add the parameter -b to the line:

print command =

in the smb.conf master template.

[mats]

lpr /home/e-smith/configuration printed the configuration to my printer OK,
but I couldn't get it to print from my PC (win 98).
I tried that "neat" trick :
chmod 0700 /var/spool/lpd/* and chmod 0700/var/spool/*
trying too get my Epson Stylus Color 1520 to work.
Now I can't print even from the console.

Please help, I am a newbee with linux & e-smith.

[Matt Goss]

Hey there!

That "neat trick" is a real nasty one and it screwed things up for me too!

Would an administrator please remove that post?

I'm not exactly sure what other problems will be caused by changing the permissions of everything in your spool dir, but it definately caused me some printer problems.

My temporary fix was to look on another Redhat box and see what the permissions were.
In the var spool dir the permissions were (note: i'm not an authority on this one!)

drwx------  on 'at' and 'cron'
drwxrwxrwt on 'samba' (fixing this one fixed the printing problem)
drwxrwxr-x  on 'lpd' 'mail'
drwxr-xr-x   on 'mqueue' 'rwho' 'uucp' 'uucppublic'

Those are from a redat box, and fixing the samba dir seemed to fix things up.

In the lpd folder, my epson printer's default permissions (as set by esmith) are
drwx------


I hope that helps!  I'm not a linux buff, so I'm not sure what the esmith permissions should be for /var/spool, but,

*if anyone out there who hasn't changed them would post their default dir permissions (/var/spool/*), that would be greatly appreciated!!*

Thanks!
Matt

[Charlie Brady]

Matt Goss wrote:

> That "neat trick" is a real nasty one and it screwed
> things up for me too!
>
> Would an administrator please remove that post?

I'm sorry, but we would rather not censure posts. Nobody should be using a version so old as V 4.0 beta 5, and there is a valid documented workaround in any case.

The correct permission for /var/spool is 0755.

Regards

Charlie

[Charlie Brady]

Charlie Brady wrote:

> I'm sorry, but we would rather not censure posts.

Woops - too much champagne. I meant "not censor posts".  And here's proof - my faux pas will stay.

Charlie

[Matt Goss]

Does the same permissions go for everying inside of the /var/spool directory?

I'm particularily interested in the defaults for /var/spool/samba /var/spool/lpd.

Thanks!
Matt