Cups stopps after 46 jobs for a while

Raphael Margraf

Welcome to the Linux-MS Jihad.

Where the generic response to a plaintive cry is uusually one of the following

- stick to windoze, stupe! - don't top post, stupe! - I refuse to answer your question unless you dump the entire memory image of the machine here, and include all hardware and how tight you torqued up the nuts on the case - I wouldn't be trying to do that at all, stupe. - RTFM, stupe (I mean why post here if you had found the answer there...) - Liux is God, and if you can';t make it work for you you are too stupid to won a computer. - Linux is crap, and thats why you should stick to Windoze.

In short, like most other usenet groups these are just as infested with smart alec jerks who don't actually want to help you at all. Just jerk off on some private axe they have to grind, and try and look smart to an unknown audience..

You might say this post itself is simply another example ;-)

I haven't responded to this thread before because I don't have a definitive answer..it does seem to me though that this sort of behaviour may - only may - be buttociated with a networked print card-server that gets 'full' and causes the TCP layer deep in the guts of Linux to go into 'backoff and retry' mode. For example..how does it notify the hosts that its unable to accept more data? If it simply stops responding at all..how do they then know when its ready again?

Sometimes the answer is to try a different card-server or communications protocol.