Date: Tue, 15 Jan 2002 18:10:55 -0800 (PST) From: John Polstra <jdp@polstra.com> To: stable@freebsd.org Cc: swb@grasslake.net Subject: Re: Group executable bit quit working? Message-ID: <200201160210.g0G2At248672@vashon.polstra.com> In-Reply-To: <009d01c19dfd$a434b950$021ea8c0@twinstar> References: <009d01c19dfd$a434b950$021ea8c0@twinstar>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <009d01c19dfd$a434b950$021ea8c0@twinstar>, Shawn Barnhart <swb@grasslake.net> wrote: > Just upgraded three systems to 4.5 RC-6 this weekend and I seem to have lost > the ability execute shell scripts or perl scripts that are group executable > only. > > The scripts run otherwise if I make them executable by the owner, but having > them g+x doesn't seem to be enough anymore. I have another system running > 4.4 that also exhibits this behavior, so its confusing me. > > The scripts in question the 4.5-RC system have been running for years with > permissions of 654. It works for me. However, I have an idea about why you might think it's broken. Let's say the file's modes are 654 (rw-r-xr--) and you are a member of the file's group. If you are also the owner of the file, you will not be able to execute it. But if you are _not_ the owner, you will be able to execute it. It's counter-intuitive, but the rule is that if you own the file, the owner permissions are used and the group permissions are ignored. I believe this is the traditional behavior, as I remember seeing it on other Unix systems at least 10 years ago. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201160210.g0G2At248672>