On 2/9/06, Manuel McLure <[EMAIL PROTECTED]> wrote: > Mark Knecht wrote: > > Hi Brett, > > Yes, I zapped it and tried restarting it but I get complaints. > > > Try > > pgrep cupsd > > and see if there's a PID listed. If so, do > > pkill cupsd > /etc/init.d/cupsd zap > /etc/init.d/cupsd start
Good so far: [EMAIL PROTECTED] ~ $ su - Password: lightning ~ # pgrep cupsd 8015 lightning ~ # pkill cupsd lightning ~ # /etc/init.d/cupsd zap lightning ~ # /etc/init.d/cupsd start * Starting cupsd ... [ ok ] lightning ~ # I then go to http://localhost:631 and choose Manage Printers. I see both printers which are on the network. One is on my son's FC2 machine, and is currently default. I also see the printer on the Mac. I clock on the Mac printer's 'Set as default' button. I'm taken to a page that says: Forbidden You don't have permission to access the resource on this server. This doesn't happen on the 'Print Test page' button. That one correctly sends a test page to each printer. However all other buttons result in the message above. The used to allow me to type in a password and do what I needed. I'm still quite concerned that the cupsd config files are hosed. As I've said there is nothing in the printers.conf file except a couple of header lines. > > What's probably happened is that etc-update updated the > /etc/init.d/cupsd script so it changes the location where it stores the > PID it has to kill when you do a "stop", therefore running > /etc/init.d/cupsd fails to kill the actual cupsd process. Since a cupsd > is already running (the old cupsd) you can't start a new one since > they'd compete for ports. > > For this reason I usually do a "/etc/init.d/<service> stop" before > allowing etc-update to update any file in /etc/init.d, and then start it > again after the update. Probably a good idea. Thanks, Mark -- [email protected] mailing list
