Dimitris Kogias wrote:
Bart Samwel wrote:
Hi Dimitris,
I don't mind including the script, but can you explain to me how it works?
I mean, why does it help to HUP ksysguardd *after* the module unload has
already failed?
Cheers,
Bart
Hi Bart,
From what I remember (I've since switched that laptop to Kubuntu)
ksysguardd was keeping some of the /proc/acpi/battery/BAT0/* files open.
The module did manage to load, IIRC, but because of the files still
being open it could not create new ones with the up to date information.
As you can probably tell I'm not intimately familiar with the vfs layer
and how modules create /proc and /sys files, but that's the behavior I
had observed on the system, using lsof(1).
Again, this is all from memory, but I'm pretty confident that's how it
worked. With Kubuntu I'm using guidance-power-manager to monitor the
battery instead of ksysguard so I haven't tried/needed this trick.
You can try using lsof to see if ksysguardd is still "hogging" these
files in your system.
Thanks for the feedback. I'll take a look at it!
Cheers,
Bart
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
