Anybody had luck with keeping Cups printing going
I have used Cups under Slackware and Cups crashed. I reinstalled everything and it would not work again.
I installed Cups under Suse 9.1 and it worked great but it crashed for no reason. I looked up the error message and learned somehow I had to add my machine in Hosts.allow. It worked again.
After some time Cups died under Suse 9.1 again! It was not the same problem. I reinstalled it and it would not work again.
Why do I have such a bad time with CUPS ? Cups is great if it would just keep on working. I have soooo much time invested in fixing cups.
The company that writes cups also has a commercial software. Do you think there are intentinal bugs in it ? Do others have cups working for years without strange 100% crashes that can not seem to be fixed ?
Should I be using something else to print with ? I tried lprng and it seemed very pale in comparison for graphics.
I installed Cups under Suse 9.1 and it worked great but it crashed for no reason. I looked up the error message and learned somehow I had to add my machine in Hosts.allow. It worked again.
After some time Cups died under Suse 9.1 again! It was not the same problem. I reinstalled it and it would not work again.
Why do I have such a bad time with CUPS ? Cups is great if it would just keep on working. I have soooo much time invested in fixing cups.
The company that writes cups also has a commercial software. Do you think there are intentinal bugs in it ? Do others have cups working for years without strange 100% crashes that can not seem to be fixed ?
Should I be using something else to print with ? I tried lprng and it seemed very pale in comparison for graphics.
I haven't had any problems with Cups on RedHat, Fedora, or RedHat Enterprise Linux. Maybe your problems are more related to the printers you are using or the network environment. Could you tell us more?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Jlevie:
It is just the simplest setup. Just an epson 880 hooked directly to the computer. It is just a "single computer network".
PsiCop, I appriciate what you have said. It is darn great software if it would stay running. I spent 100$ after a long fight with cups to upgrade to SUSE Pro. What I can not understand is why ripping it out and reinstalling it does not solve it. Are there files in /etc that are getting messed up. Is there a way to see what files an RPM writes to ( under /etc). Is there an rpm command to "live wild and dangerously, write over all old settings"?
It is just the simplest setup. Just an epson 880 hooked directly to the computer. It is just a "single computer network".
PsiCop, I appriciate what you have said. It is darn great software if it would stay running. I spent 100$ after a long fight with cups to upgrade to SUSE Pro. What I can not understand is why ripping it out and reinstalling it does not solve it. Are there files in /etc that are getting messed up. Is there a way to see what files an RPM writes to ( under /etc). Is there an rpm command to "live wild and dangerously, write over all old settings"?
Can you have a look at logs in /var/log, instead of reinstalling your system every day, Linux is a bit different from windows you know.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
jlevie:
what cups does is que up and just sit there.
Your solution sounds very good. Cups has worked fantastic and then just quits. One time I had to add "allow 127.0.0.1" and the next time it failed in a way that that would not fix it. This is three times cups has done this to me and on two totaly different distros. Slackware and Suse are about as far apart as two linux distros can go.
what cups does is que up and just sit there.
Your solution sounds very good. Cups has worked fantastic and then just quits. One time I had to add "allow 127.0.0.1" and the next time it failed in a way that that would not fix it. This is three times cups has done this to me and on two totaly different distros. Slackware and Suse are about as far apart as two linux distros can go.
> what cups does is que up and just sit there.
Which sounds like Cups can't talk to the printer. That could be caused by a problem with interrupt delivery for the parallel port or some othe flaw on the motherboard. Or it could be that the printer is just not working right and Cups never sees the printer as ready to print. Or it could be a communication problem with the printer and data is just not reaching the printer correctly.
The first thing I'd do is to see if there's a BIOS update for your motherboard. Wierd problems like this have been known to cured by a BIOS update. The other thing I'd do is to disable PnP mode in the BIOS setup if you have that option. Also it wouldn't hurt to try a different parallel cable (one of the good quality IEEE 1284 cables).
Which sounds like Cups can't talk to the printer. That could be caused by a problem with interrupt delivery for the parallel port or some othe flaw on the motherboard. Or it could be that the printer is just not working right and Cups never sees the printer as ready to print. Or it could be a communication problem with the printer and data is just not reaching the printer correctly.
The first thing I'd do is to see if there's a BIOS update for your motherboard. Wierd problems like this have been known to cured by a BIOS update. The other thing I'd do is to disable PnP mode in the BIOS setup if you have that option. Also it wouldn't hurt to try a different parallel cable (one of the good quality IEEE 1284 cables).
ASKER
Actually I tried this on two different computers, USB and Parallel, Two different linuxes and it just stopped working. I am going to build the system and try 'rpm --verify cups'. I will also backup the /etc directory as soon as I have it all working.
Trying this on two different computers and two different I/O methods tends to point to the printer itself as being the cause.
Hmm, the printer is the only device connected to the parallel port, right?
Hmm, the printer is the only device connected to the parallel port, right?