Bug#327599: Fwd: Bug#327599: korganizer: alarm daemon causes periodic disk spin up in laptop mode

2005-09-13 Thread Bart Samwel
Thomas Uttenthaler wrote: An aside: Do you mount /tmp as tmpfs? That might help if these are files in /tmp. Aaa. I just removed this some days ago because I couldn't remember what this was good for ... it works much better now, although kmail still dirties inodes in ~/.kde/share/... . it

Bug#327599: Fwd: Bug#327599: korganizer: alarm daemon causes periodic disk spin up in laptop mode

2005-09-12 Thread Thomas Uttenthaler
Am Sonntag, 11. September 2005 23:15 schrieben Sie: Thomas Uttenthaler wrote: here comes some dmesg output below [1]. I've discovered, that kmail (and the kmail mini icon program) also has this nasty behaviour (about every 60 seconds), of course with automatic checks for new mail

Bug#327599: korganizer: alarm daemon causes periodic disk spin up in laptop mode

2005-09-11 Thread Thomas Uttenthaler
Package: korganizer Version: 4:3.3.2-3 Severity: normal I discovered, that the korganizer alarm daemon [1] causes a disk spin-up in laptop-mode about every 60 seconds. this is not only annoying but also lifetime limiting to the disk. the default value for idle timeout is 5 seconds (see package

Bug#327599: Fwd: Bug#327599: korganizer: alarm daemon causes periodic disk spin up in laptop mode

2005-09-11 Thread Bart Samwel
Thomas Uttenthaler wrote: I discovered, that the korganizer alarm daemon [1] causes a disk spin-up in laptop-mode about every 60 seconds. this is not only annoying but also lifetime limiting to the disk. the default value for idle timeout is 5 seconds (see package laptop-mode-utils). so there

Bug#327599: Fwd: Bug#327599: korganizer: alarm daemon causes periodic disk spin up in laptop mode

2005-09-11 Thread Bart Samwel
Thomas Uttenthaler wrote: here comes some dmesg output below [1]. I've discovered, that kmail (and the kmail mini icon program) also has this nasty behaviour (about every 60 seconds), of course with automatic checks for new mail deactivated. Maybe I file another bugreport about this tomorrow.