s.voss@terradata.de
steve@epic.co.uk
Mike.Phillips@cambridge.simoco.com
rauthenberg@HHI.DE
chad@sequana.com
and many others
Original Question
Anyone Knows the reason for this?
___________________________________________________________________________
Your request hp4-9 destined for hp4
The job title was: stdin
submitted from: botafogo
at: Fri Mar 14 08:51:18 1997
encountered an error while printing on printer hp4. Printing stopped with
an exit code of 1.
Reason for failure:
/etc/lp/interfaces/hp4: /dev/null: cannot create
Procmail and samba complain about the same thing
/dev/null: cannot create
___________________________________________________________________________
Answer
___________________________________________________________________________
The problem wasn't in /dev/null. It had the right permissions.
lrwxrwxrwx 1 root root 27 Jan 9 1997 null -> ../devices/pseudo/mm@0:null
The problem was in /devices/pseudo/mm@0:null
It has some crazy permission to a unique user 'lp' and group other
crw------- 1 lp other 13, 2 Oct 12 12:48 mm@0:null
And must be
crw-rw-rw- 1 root sys 13, 2 Oct 12 12:48 mm@0:null
Stefan <s.voss@terradata.de> really hit the spot and was very kind to send
me a step by step mail showing me the problem. Sometimes admintool
change the permissions when you create a printer. I've just created a
printer using admintool.
My opinion is that this must be a incredible bug. How can admintool change
the permissions in /devices/pseudo/mm@0:null when you create a printer
using admintool itself so that the printer you're trying to make work
don't work!!!
Very Thanks
Reinaldo