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

[Joe Linux]

I don't really want to change it recursively.  Just locking the main 
folder should be enough.  It's fine during the short period it stays 
changed.

I appreciate your help, but my observation and belief is that Linux is 
damn user unfriendly.  I used Libranet 1.9.1 for a long time.  I don't 
remember this same sort of problem, but I can't be sure.  That was the 
best Linux I ever used, but it went out of date.  Then their 2.0 was a 
generalized mess.  I believe they are still trying to fix it.

David Jackson wrote:

>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
>>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cluedenver.org/pipermail/clue-tech/attachments/20020522/19d74160/attachment.html