[CLUE-Tech] Re: I tried the 'chattr +i'

David Jackson david.j.jackson at pickledbeans.com
Wed May 22 16:59:16 MDT 2002


Joe --
You have to use -R flag for recursive.
This is a bandaid solutions you need to find the script that runs
a schedule job that does this.

su - # not su
crontab -l # this will tell you what jobs are scheduled as to run automaticly
as part of root cron.

David


> I tried the "chattr +i" idea on another user but I got an error
> message.
> 
> [jl at localhost jl]$ su
> Password:
> 
> [root at localhost jl]# chattr +i /home/ru
> chattr: Inappropriate ioctl for device while reading flags on /home/ru
> [root at localhost jl]#
> 
> [root at localhost jl]# chattr +i 770 /home/ru
> chattr: No such file or directory while trying to stat 770
> chattr: Inappropriate ioctl for device while reading flags on /home/ru
> [root at localhost jl]#
> 
> 
> Jed S. Baer wrote:
> 
>>On Wed, 22 May 2002 14:08:30 -0600
>>Joe Linux <joelinux at earthlink.net> wrote:
>>
>>>After a great deal of time consuming effort, I thought I had the 
>>>Mandrake permissions problem solved, but now they have come back as 
>>>before -
>>>755.  It seems rather odd to me that on a multi-user system that one 
>>>user can peer into another users files, and you can't do anything to 
>>>stop it.
>>>
>>
>>Hey, on my system, I can set file permissions so even I can't see my
>>own files. ;-)
>>
>>>Mandrake Linux is like a glass house with no window shades.
>>>
>>
>>Well, you know what they say: Those who live in glass houses shouldn't
>>throw stones.
>>
>>Seriously, AFAICT, this is unique to your system. Finding it might in
>>fact be a major pain. IIRC, the original problem was that some program
>>is changing the permissions on a file? Maybe someone already suggested
>>this, but, as root, do a chattr +i {name of file}. This will make the
>>file "immutable". Then you can look through your log files, or maybe
>>your cron status e-mails (sent to root, most likely), for a program
>>reporting an error on {name of file}.
>>
>>Presumably, you've looked through all the stuff that runs in the
>>various /etc/cron* directories for culprits?
>>
>>jed


-- 





More information about the clue-tech mailing list