Problem: permission bits changed on files automatically
Anybody have any experience with this? On an intermittent basis, all of the files in my home directory with mode 0775 are changed to mode 0675 without my knowledge. I've checked the cron jobs for root to see if anything looks out of place, but nothing shows up. I'm running SuSE 8.2, with everything up to date, but this has been happening since version 7.3, it's just now become so frequent that I've decided I have to resolve it. I usually discover the problem when shell scripts or Perl scripts suddenly stop working when I call them from either the command line or cron. My SuSE system is on DSL, with a D-Link 604 DSL router, an internal network with Windoze 2000 (two laptops and a desktop) and an old SCO Unix 5.0 box. I have Samba 2.2.7a running to allow the Windoze boxes to use the SuSE box as a file exchange point, McAfee virusscan is installed on all Windoze boxes. I do cross-platform database development using Linux, Windoze, and Unix, but my primary box and my desktop are Linux. Windoze is there solely for development purposes. I've been a Unix/Linux system administrator for 15 years - my firs Unix box was a Unisys Tower (re-badged NCR Tower) with a Motorola 68020 processor and NCR Tower Unix (AT&T SystemV release 2.5). Things have come a mightly klong way since then. At any rate, if anyone can shed any light on this, it would be appreciated. -- --------------------------------------------------- Dave Grosvold dave@rcanyon.com ---------------------------------------------------
On Fri, 2003-10-03 at 10:50, David C. Grosvold wrote:
Anybody have any experience with this?
On an intermittent basis, all of the files in my home directory with mode 0775 are changed to mode 0675 without my knowledge.
I've checked the cron jobs for root to see if anything looks out of place, but nothing shows up.
I'm running SuSE 8.2, with everything up to date, but this has been happening since version 7.3, it's just now become so frequent that I've decided I have to resolve it.
I usually discover the problem when shell scripts or Perl scripts suddenly stop working when I call them from either the command line or cron.
My SuSE system is on DSL, with a D-Link 604 DSL router, an internal network with Windoze 2000 (two laptops and a desktop) and an old SCO Unix 5.0 box.
I have Samba 2.2.7a running to allow the Windoze boxes to use the SuSE box as a file exchange point, McAfee virusscan is installed on all Windoze boxes.
I do cross-platform database development using Linux, Windoze, and Unix, but my primary box and my desktop are Linux. Windoze is there solely for development purposes.
I've been a Unix/Linux system administrator for 15 years - my firs Unix box was a Unisys Tower (re-badged NCR Tower) with a Motorola 68020 processor and NCR Tower Unix (AT&T SystemV release 2.5). Things have come a mightly klong way since then.
At any rate, if anyone can shed any light on this, it would be appreciated.
-- --------------------------------------------------- Dave Grosvold dave@rcanyon.com ---------------------------------------------------
Let me guess, the permissions changed after a reboot. If that is the case look at the /etc/permissions.* files as that is where the permissions are set for many files. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998
Ken: On Friday 03 October 2003 10:08 am, Ken Schneider wrote:
Let me guess, the permissions changed after a reboot. If that is the case look at the /etc/permissions.* files as that is where the permissions are set for many files.
Nope - that's not it, but your comment led me down a new path. Now that you mention it, it happens after the On-Line update when SuSEConfig runs. Guess what? I just had to change the setting of CHECK_PERMISSIONS in /etc/ sysconfig/security to "warn" rather than "set" and the problem is solved! Thanks for your help, Ken. -- --------------------------------------------------- Dave Grosvold dave@rcanyon.com ---------------------------------------------------
On Fri, Oct 03, 2003 at 10:38:41AM -0500, David C. Grosvold wrote:
Nope - that's not it, but your comment led me down a new path. Now that you mention it, it happens after the On-Line update when SuSEConfig runs.
Guess what? I just had to change the setting of CHECK_PERMISSIONS in /etc/ sysconfig/security to "warn" rather than "set" and the problem is solved!
but anyway, SuSEconfig should not do anything in a $HOME. What user are we talking about? root or a mere mortal? The only thing which would explain this (to me) is some weird bind-mount or symbolic link into a home, but this is pure speculation. regards, Stefan -- Stefan Seyfried Senior Consultant community4you GmbH, Chemnitz, Germany. http://www.community4you.de http://www.open-eis.com
participants (3)
-
David C. Grosvold -
Ken Schneider -
Stefan Seyfried