Date: Mon, 1 Sep 1997 22:37:55 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Hartmann <root@ipamzlx.physik.uni-mainz.de> Cc: questions@FreeBSD.ORG Subject: Re: Access bits of /dev/null Message-ID: <Pine.BSF.3.96.970901223649.3114D-100000@localhost> In-Reply-To: <Pine.BSF.3.96.970831181130.25599A-100000@ipamzlx.physik.uni-mainz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 31 Aug 1997, Hartmann wrote: > Dear Sirs. > Sometimes the system changes the access bits of /dev/null to 500, > so some applications and utilities faile because they cant't write to > /dev/null. Can anybody tell me how to solve the problem? It seems > trivial, but changing the access bits have had no effect because > after a while the system overrides these changes. I don't know where > these changes are made, neither by cron, nor by rc. > > Has anybody ideas or a solution? Or is the problem a problem because > managing a FBSD isn't my favourite profession ;-)) You must have some evil program or user changing the settings. I know that none of the system standard utilites that I run do this. You might try changing the owner and group to something else, which should keep the offending program from changing the permissions, unless it's running suid root, which would help limit your search. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970901223649.3114D-100000>