I used visudo to edit the sudoers file and created a group that would be allowed to use the /etc/init.d/cups restart command as root without using a password, as well as some other printing commands. When i use the command

sudo /etc/init.d/cup restart

This is what shows.

-n Shutting down cupsd
/etc/init.d/cups: line 98: killproc: command not found
-en -en
-en -en -
-en failed-en -en
-en -en

-n Starting cupsd
/etc/init.d/cups: line 88: startproc: command not found
-en -en
-en -en -
-en failed-en -en
-en -en

It obviously doesn't restart cups, however, if I execute this command as root it works fine. This is Suse 8, HP330 ML. I have had problems with cups dying off at this install, I didn't get any responses on that thread. so I was trying to be able to have my users be able to start this up with out me dialing in every morning. A girl needs her Beauty sleep, can anyone shed some light on my sudo problem.

Thanks

:D

Not knowing what your /etc/init.d/cups' line
98 and 88 look like it's hard to asses ... but
rather than wrapping a kludge around the failing
process: did you push the debug level up in
cupsd.conf and check the error logs to see
WHY it's dying?


Cheers,
Tink

I might be on to the problem. First we had a uni-directional cable on the printer. Changed that. Then we had two entries in yast for a network printer and the parallel printer. Removed the network printer and that seems to get rid of the the not responding error. So fingers crossed it may be resolved. Thanks for your help though