Printques use "all" CPU - stop/start needed
Imported from the Apple Support Forums via the Wayback Machine 🔗
Sorry if this has been discussed before:
Anybody know why OSX Server printserver printqueues could start "stealing" almost all CPU cycles when it has been running for a couple of days?
We have to stop and restart the printserver in Server Admin to release the CPU "hogging".
We have a small script that removes old files from /var/spool/cups and /var/spool/cups/tmp to keep those folders clean because earlier these folder filled up and the queues stopped as a result of that.
Maybe the script confuses the printserver sw when trashing the files without the printserver nowing it?
I'm thinking of looking at stopping and restarting printserver with a script (using "serveradmin"?) once a day or someting if I find no other solution.
0 replies
Sign in or join Beachball Help to reply.