Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!math.fu-berlin.de!opal!unido!mcshh!akes From: akes@mcshh.hanse.de (Andreas Kessemeier) Newsgroups: comp.unix.misc Subject: Re: Sticky bit? Keywords: sticky, directory Message-ID: <8826@mcshh.hanse.de> Date: 25 Mar 91 18:56:20 GMT References: <6704@navy28.UUCP> Distribution: comp Lines: 26 gilbertd@p4.cs.man.ac.uk (Dave Gilbert) writes: >In <6704@navy28.UUCP> seda@motcid.UUCP (Joseph W. Seda) writes: >>What does the stick bit do? >As far as I'm aware what it does is do something like try and keep programs >in memory -so that say you have 20 people using vi on a machine, it ould >only hold 1 copy and also it would keep it in memory so its available immediatly Sorry, but only a half hit :-) The sticky bit doesn't tell the system to hold the job in memory. This can only be done with lock(S) and is very dangerous, because it can lead to complete deadlock. The sticky bit tells the kernel to not delete the copy of the text- segment in swapspace after use. If the programm is called next time it is much cheaper to grab the text out of swap rather than reading the file. This is because swap is always physikal sequential on disk while a file may be fragmented. On the other hand, the overhead for reading out of swap is much less than reading a file. Greets, Andreas -- Andreas Kessemeier akes@mcshh.hanse.de There is no way to Freedom. Freedom is the way.