- This topic has 7 replies, 5 voices, and was last updated 15 years, 6 months ago by
.
-
Topic
-
-
Replies
-
-
-
Well two issues. Simplest one is that if you are a user other than “hci” even though you are in the same group ‘staff’ you cannot ‘cd’ into ‘LogHistory’. If it were the lowrcase “s” I thing that allows for changing into the directory, but not for the capital “S”. We use the lowercase “s” for our OutboundSave and InbounSave directories w/o problems.
Second is, well, I was hoping to understand why this was done. What I’d really like to do is create LogHistory directories as links in advance. We like to keep our archive stuff outside of our process directory space. But, it seems like it was not working right when I tried creating the links in advance.
Kevan
-
-
S and s are referred to as the “Sticky Bit” in Unix. The Sticky Bit is usually associated with world writeable directories, such as the /tmp directory. This prevents users from deleting files they don’t own. Users can write to those directories but only they can delete or update those files they own. It’s commonly used for scratch directories like /tmp to provide some security for otherwise world-writable directories.
The S means that someone applied the Sticky Bit security to r–. The s means they applied the Sticky Bit security to r-x. The underlying problem is that you are not getting xecute permission, which is preventing you from changing to the directory, the S vs. s just hightlights the problem. You need to set the umask of the user to make sure new directories are created with group permission of r-x or rwx. This will change your S to s.
Hope this helps,
Robert Milfajt
Northwestern Medicine
Chicago, IL -
-
-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
