On Wednesday 16 November 2005 7:55 am, Holger Macht wrote:
On Mon 14. Nov - 10:43:21, Tom Cada wrote:
I ran into problems starting acpid on my laptop. I traced it down to a log file (/var/log/acpid) being over 2 GB in size. When I renamed the log file, acpid would start properly.
Does anyone have a solution to this problem, such as a script run by cron, to rename the file on a weekly basis or some other such thing?
Is this something that should be built into /etc/init.d/acpid to control this problem? I'm asking this in the sense of improving the general operation of the distribution for users who have limited technical abilities.
This should be already fixed. Remove the logfile and run the you update and the problem should not appear again.
Tried it and it appears to have worked. Before the update, acpid was going into a loop condition that generated many error messages, filling the log file, along with grabbing all available cpu cycles. A further question though. Can running YOU step on already installed programs that have been modified to meet the SLICK requirements? I guess I am wondering if the kernel can be inadvertently upgraded, loosing the CK patches? Thanks...Tom.