Thank you, I really need this. I woke up this morning again to a broken cpu. Overnight night cups logged another 56gig if error messages. I need to find out what's broke but in the mean time limiting the size will help. I'm running on a solid state drive and I am afraid all this writing is going to damage it.
Unfortunately, the config file shows this
- Code: Select all
# Deactivate CUPS' internal logrotating, as we provide a better one, especially
# LogLevel debug2 gets usable now
MaxLogSize 0
I'm not sure what "A better one" means. However the log in question is the error_log. But it is the locked log file (either needs to be root, or I don't know).
I deleted the log in order to boot. By the time I went to the log to see if it changed it was already 18gig. I tried a root mouspad to view the log but it hung. I am kind of stumped as to how to read the log file.
The bootup process hangs at
- Code: Select all
Started update UTMP about System Runlevel Changes
So my startup consists of alt+f1 to terminal at the hangup, login to wayne and run startx to GUI.
Kind of a cluster-#$$%.
I'm still researching the UTMP hangup but it is inconclusive so far.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q