| 1 |
KH wrote: |
| 2 |
> Dirk Heinrichs schrieb: |
| 3 |
> |
| 4 |
>> Am Mittwoch 10 Juni 2009 20:55:16 schrieb Paul Hartman: |
| 5 |
>> |
| 6 |
>> |
| 7 |
>>> I had a similar problem, 100% cpu usage caused by a daemon that did |
| 8 |
>>> not respond well when network connection was lost. My |
| 9 |
>>> /var/log/messages grew over 60GB in a few hours with the same message |
| 10 |
>>> repeated tens of millions of times. |
| 11 |
>>> |
| 12 |
>> Well, that's the reason you should put /var on its own partition/logical |
| 13 |
>> volume. |
| 14 |
>> |
| 15 |
>> Bye... |
| 16 |
>> |
| 17 |
>> Dirk |
| 18 |
>> |
| 19 |
> |
| 20 |
> Well something creating that much messages is just buggi! The cpu will |
| 21 |
> be on havy duty no diffrence where /var is mounted. This is a bug which |
| 22 |
> should not happen. |
| 23 |
> |
| 24 |
> kh |
| 25 |
> |
| 26 |
> |
| 27 |
> |
| 28 |
|
| 29 |
My messages file gets huge sometimes too. Usually when hal or something |
| 30 |
doesn't unmount the DVD drive and it just spits out error after error |
| 31 |
about every two seconds. |
| 32 |
|
| 33 |
Let's not get started on how buggy hal is. That could turn into a huge |
| 34 |
thread for sure and could lead to discussions about xorg-server and the |
| 35 |
recent upgrade. |
| 36 |
|
| 37 |
Dale |
| 38 |
|
| 39 |
:-) :-) |
Archives