Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Some implementations of the ls command use L to denote the set-group-id bit, whereas you usually see a S. The uppercase L means that the execution bit is not set, otherwise you would see a lowercase l. The same applies when ls shows it as S or s.
An example of an executable with the setgid bit set is the command wall. In this case the l should be lowercase, since the execution bit is set. Check it on your system to verify:
Code:
ls -l `which wall`
At this point I'm curious... which system are you running on and what implementation of the ls command is this?
Lastly, you can find some information about the L permission bit here.
Some implementations of the ls command use L to denote the set-group-id bit, whereas you usually see a S. The uppercase L means that the execution bit is not set, otherwise you would see a lowercase l. The same applies when ls shows it as S or s.
An example of an executable with the setgid bit set is the command wall. In this case the l should be lowercase, since the execution bit is set. Check it on your system to verify:
Code:
ls -l `which wall`
At this point I'm curious... which system are you running on and what implementation of the ls command is this?
Lastly, you can find some information about the L permission bit here.
Ok, there are differences from system to system on how permissions are set. On which system do you see the L behaviour anyway?
Quote:
Thanks for the info. But if executable bit is not set, then it should remain blank.
Good point! Indeed the setgid bit has a different meaning if applied to executables, not-executables or directories:
1. on executables: the user who executes the program gains privileges of the group to which the file is assigned.
2. on not-executables: processes are granted to use the mandatory locking on these files. See this document for details: http://kernel.org/doc/Documentation/...ry-locking.txt
3. on directories: this causes new files created inside the directory to inherit its group ID.
Ok, there are differences from system to system on how permissions are set. On which system do you see the L behaviour anyway?
Good point! Indeed the setgid bit has a different meaning if applied to executables, not-executables or directories:
1. on executables: the user who executes the program gains privileges of the group to which the file is assigned.
2. on not-executables: processes are granted to use the mandatory locking on these files. See this document for details: http://kernel.org/doc/Documentation/...ry-locking.txt
3. on directories: this causes new files created inside the directory to inherit its group ID.
Thanks colucix for the nice info.
Actually I got it on an very old Unix System ( IRIX 6.5 ).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.