Path: utzoo!attcan!uunet!decwrl!shelby!rutgers!mcnc!uvaarpa!murdoch!amber.cs.Virginia.EDU!rwl
From: rwl@amber.cs.Virginia.EDU (Ray Lubinsky)
Newsgroups: comp.windows.x
Subject: Re: window manager swapping (was Re: Another R5 wish)
Message-ID: <1990Sep25.132603.13572@murdoch.acc.Virginia.EDU>
Date: 25 Sep 90 13:26:03 GMT
References: <235@grapevine.EBay.Sun.COM> <9009041636.AA23617@hansen.com> <489@zok.UUCP>
Sender: news@murdoch.acc.Virginia.EDU
Reply-To: rwl@uvacs.cs.Virginia.EDU
Organization: UVa Computer Science Dept.
Lines: 31


In article <489@zok.UUCP>, mark@zok.UUCP (Mark W. Snitily) writes:
:
|> Quoting from the man page:
|>     "If an executable file is set up for  sharing  (this  is  the
|>      default)  then  mode 01000 (save text image after execution)
|>      prevents the system from abandoning the swap-space image  of
|>      the program-text portion of the file when its last user ter-
|>      minates."
|> 
|> In other words, it won't get swapped out.  The con is that it'll always
|> be there, but you'd probably want to keep the window manager in memory
|> anyway.


Nope.  Sorry.  It means that the text portion of the process will not be
removed from the swap partition on the disk (not main memory) which is just
what the man page says.

This is only of potential advantage when you have a program like a shell (or
window manager) where you'd like to avoid the overheading of finding the file
on disk the next time you start it up.  On a busy multiuser system, setting the
sticky bit on a popular program has little affect because there's rarely a time
when *someone* isn't running it.  In this case the text portion of the process
is always on the swap track anyway.


| Ray Lubinsky                           rwl@uvacs.cs.Virginia.EDU (Internet) |
|                                        rwl@virginia                (BITNET) |
| Department of Computer Science,        ...!uunet!virginia!uvacs!rwl  (UUCP) |
| University of Virginia                 (804) 982-2219               (voice) |