If you have high CPU usage on your mac, and the culprit is the "socket" process, "lprm -" fixes it!
From comments I read on the web and my own experience, it would appear that some print drivers installed on your windows VM can get a page stuck in the queue. How cupsd or the socket process gets involved is unknown to me.
If you have high CPU usage on your mac, and the culprit is the "socket" process, "lprm -" fixes it!
ReplyDeleteFrom comments I read on the web and my own experience, it would appear that some print drivers installed on your windows VM can get a page stuck in the queue. How cupsd or the socket process gets involved is unknown to me.
According to my experiences helps rather:
ReplyDelete# cancel -a
E.
Which 2 of the following commands list all standing print jobs and their status
ReplyDeletelpstat -t
ReplyDelete