The Saturday 2003-12-27 at 07:51 -0500, James Finnall wrote:
The format of the printer would not really be an issue here, once ghostscript (if required) has run to produce the output file nothing left but sending the output file to the printer.
True enough, but I'm grasping at straws here :-)
However, I have canceled large photo jobs under the Slack system and the ghostscript child is canceled as well if it was still running.
Before SuSE 8.1/8.2, when I did not use cups, I cold cancel jobs easily. The ghostscript child is no problem, that one ends before printing actually starts, I think. The problem is the child program that actually sends the data through the parallel port, that doesn't get killed.
When printing to a remote lpd server, the job is gone so fast that it cannot be deleted on the local machine. Nothing left there to cancel or hold. As far as CUPS is concerned it is completed. The job has to be canceled manually on the remote lpd server.
I suppose so. However, the client cups could perhaps talk to the server cups and stop the job. Not my case.
The following lines are the file info on my Slack system for some of the CUPS files. It would of been compiled on Jun 12, 2002.
bash-2.05a# ls -l /usr/bin/lp root bin 11652 Jun 12 2002 /usr/bin/lp bash-2.05a# ls -l /usr/sbin/cupsd root bin 235404 Jun 12 2002 /usr/sbin/cupsd bash-2.05a# ls -l /usr/bin/lprm root bin 6700 Jun 12 2002 /usr/bin/lprm
I would be interested on the permissions of this one. Any suid bits around?
If your files are the ones from the distro and all match the way they should, perhaps a custom build of CUPS would resolve the problem.
Sorry, I cannot help on the security issue, I always login as root.
Ah! I never do, that could be it. Next time, I'll try to stop the job as root. I have to run some more tests, enabling first debug logging of the cps daemon.
However, I think I did have to make some mods to the CUPS config in /etc/cups to get the some operations to work though. Not sure which ones though.
Yes, me too, for the web interface to work. Commented on the list months ago.
The web interface now prompts me for the root login and password. If I recall I had to do this even though I was logged in as root. I thought it was about security issues for a web interface and some operations would require a 2nd authentication to enable them.
It is, I guess, because the web interface doesn't know that you are root, till you log with it. It doesn't matter that the browser is running as root.
Perhaps it will be of some help to you.
Some ideas, yes, thanks. -- Cheers, Carlos Robinson