30 Mar
2012
30 Mar
'12
4:20 p.m.
On 03/30/2012 11:06 AM, Darrell Anderson wrote:
ops, looks like our messages crossed paths too quick!
:)
Yes, I have a "cleanup" script in my Slackware system. After my experience
yesterday I added some snippets in that script to perform this newly required
housekeeping.
Yet I think this type of effort indicates a flaw with tsak presumptions. I don't
think we should presume that systems perform automatic housekeeping chores. As tsak runs
only when using TDM, TDM should perform that cleanup on a reboot/halt request.
100% correct - not all distros do housekeeping to automatically wipe /tmp in
between boots (with good reason). Many have housekeeping scripts that are set
at 14, 30, 60 days, etc... and daily checks of /tmp size to warn of disk size
issues.
Any application that does not do its own housekeeping is broken and need to
clean up its act. If you never take out the trash -- your house begins to
smell - quickly :)
The fact that a reboot does not stop tsak is evidence that this housekeeping is
necessary. Most people will disable tsak from within KControl. When they do that they
expect tsak to disappear on the next reboot or X server restart. When a user disables tsak
from within KControl, those pipe/socket files should be flushed immediately right then and
there.
tsak is a good idea but we have a few bugs to quash. :)
As I mentioned in my previous message, I did not notice any runaway CPU hogging. I tested
in both a virtual and physical machine. I would test further but can't use tsak at all
because of the Ctrl-Alt-Delete conflict with TDM.
I have runaway cpu with tsak and tdmtsak - EVERY TIME until I:
sudo killall tsak
sudo killall tdmtsak
As noted in the bug report, after killing tsak, cpu use drops from 100%, but
tdmtsak continues to eat ~20% of the cpu until it is killed.
--
David C. Rankin, J.D.,P.E.