You are misreading the man page. The t switch uses swap, the s switch sets
the user or group ID on execution.
I'm probably going to do a lousy job of explaining it, but I'll give it a
stab anyway.
This is the heart of the user provate group scheme being useful. We are
all in our own group, which in the traditional unix way seems like a bad
idea. The problem with the traditional way is that when you want to be in
multiple groups, you always default to one of them. So if I'm in m,ore
than one development group say, and default to dev1, when I work in the
dev2 source tree, all the fiels I create have the group dev1. Bummer. The
dev2 boys may not be able to use them properly. So, the beauty of the user
provaye group scheme is that you set the sticky bit to control the group
id on all files under a directory. So if the dir /share/dev2 has the
sticky bit set (with the group id dev2) then, when I cd over to
/share/dev2 and work there, all files are created with the group dev2. ANd
the same applies for a simlar setup for say /share/dev1.
I hope that weas even remotely clear or useful.
charles
On Wed, 1 Dec 1999, Pieckiel, Kevin A wrote:
> Would someone please clearify what the purpose of the "sticky" bit is and
> how it is used? I understand the concept of the set{u,g}id bits, but this
> one is strange. I don't see how saving a program on the swap device would
> be beneficial unless the swap device was faster than the media on which the
> program was stored originally. For Linux, my swap is just another HDD
> partition.
>
> And then other questions arise: How long does it stay in swap? How do I
> remove it from swap? What kinda of apps in what kinds of circumstances
> would benefit from the sticky bit?
k
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
