<html>
<head>
</head>
<body>
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.<br>
<br>
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.<br>
<br>
David Jackson wrote:<br>
<blockquote type="cite" cite="mid:1514.63.165.194.52.1022108356.cqhost@webmail.cqhost.com">
<pre wrap="">Joe --<br>You have to use -R flag for recursive.<br>This is a bandaid solutions you need to find the script that runs<br>a schedule job that does this.<br><br>su - # not su<br>crontab -l # this will tell you what jobs are scheduled as to run automaticly<br>as part of root cron.<br><br>David<br><br><br></pre>
<blockquote type="cite">
<pre wrap="">I tried the "chattr +i" idea on another user but I got an error<br>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><br></pre>
<blockquote type="cite">
<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><br></pre>
</blockquote>
<pre wrap="">Hey, on my system, I can set file permissions so even I can't see my<br>own files. ;-)<br><br></pre>
<blockquote type="cite">
<pre wrap="">Mandrake Linux is like a glass house with no window shades.<br><br></pre>
</blockquote>
<pre wrap="">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<br>fact be a major pain. IIRC, the original problem was that some program<br>is changing the permissions on a file? Maybe someone already suggested<br>this, but, as root, do a chattr +i {name of file}. This will make the<br>file "immutable". Then you can look through your log files, or maybe<br>your cron status e-mails (sent to root, most likely), for a program<br>reporting an error on {name of file}.<br><br>Presumably, you've looked through all the stuff that runs in the<br>various /etc/cron* directories for culprits?<br><br>jed<br></pre>
</blockquote>
</blockquote>
<pre wrap=""><!----><br><br></pre>
</blockquote>
<br>
</body>
</html>