Thanks for the suggestions, but an lprng <-> cups mismatch wasn't it.
I removed both cups and lprng, then reinstalled cups. Tried to start cups using /etc/rc.d/rc.cups. No go. Still got the error 98. So, I thought I would reboot and see if that did anything. (I normally don't reboot to fix problems - this isn't a Windows box - and sometimes it can make things worse. Anyway...) While the machine was booting up and still in BIOS phase, I realized that the only thing that had changed on this machine recently other than the new kernel was the Terrarec Cinergy T2 USB DBV-T adapter I attached to it. So, I pulled it. Machine booted, and cups started normally. I printed something to make sure. Then I stuck the T2 back in and rebooted. Cups refused to start the scheduler - error 98. I pulled the T2 again, and then tried to start cups without rebooting. No go. Rebooted. Cups started again like a charm. Therefore, I believe the problem I am having has to do with the Cinergy T2 and some conflict with cups. I just plugged in the adapter, and cups still prints, so it either has to do with having the adapter plugged in during boot or with something I haven't discovered yet. (Udev/hotplug seem like good suspects.) I guess I will watch some TV and then see if I can print. |
cups
Hi,
After googling for 1 hr, I just asked a friend and he solved the problem in 1 min: netstat -ant |grep 631 to know wich process is using the port --------------------------------- rpc.mount was using the 631 port (rpc.mount uses dynamic ports) /etc/init.d/nfsserver stop To stop nfs /etc/init.d/cups start To start cups /etc/init.d/nfsserver start To start NFS |
Anther easy way of finding the user of a port is with fuser.
Code:
root@sonic:~# fuser -v 631/tcp |
All times are GMT -5. The time now is 10:56 AM. |