recurring perms problems

[Gene Heskett]

Greetings;

About 1 or 2x a week, I discover something that isn't working due to perms.

Specifically my stuff is suddenly owned by root.  I ran clamtk this morning 
and scanned my home dir recursively. From a cli.

When I had exited clamtk, I noticed that it had complained in the cli that 
it had no permissions to look at my crontab file in 
/var/spool/cron/crontabs.

Gaining root, no surprise, but /var/spool/cron/crontabs/gene, which is 
still working because my sig is still being updated every 5 minutes, but as 
me, I get a no perms when I enter "crontab -e" because its owned by 
root:root!

I didn't do that.  And this sort of thing is gradually getting old.  I did 
not have such problems with the previous distros.

I know that logrotate can muck things up logwise and I can't recall an 
install where I didn't have to modify logrotate, but that gets old too, so 
the logs I want to keep are gradually being moved to ~/log where I can do 
the housekeeping needed.

But I don't see how this can be blamed on logrotate.

Has anyone a clue to spare as to the cause of such shenanigans?

Thanks all.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
I read Playboy for the same reason I read National Geographic.  To see
the sights I'm never going to visit.