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