30 Mar
2012
30 Mar
'12
4:06 p.m.
Now I read your second mail and I see - for you was
not
enough to restart. In Debian this is sufficient, because after reboot the
system automatically clean /tmp and /var/tmp.
Oops, 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.
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.
Darrell