Re: Sticky Bits and fglgo?

In article <1993Feb2.161423.9742@magnus.acs.ohio-state.edu>, phart@magnus.acs.ohio-state.edu (Patrick S Hart) writes: |> I was wondering if you can set a sticky bit on fglgo to allow users to share a |> single copy of fglgo stored in memory. You're confusing two things. For users to share a single memory copy of fglgo (or whatever), all that's needed is for it for have been loaded as sharable, "pure text". This is the default on modern Unix systems, and fglgo is shipped that way on my system (Sparc station). Setting the sticky bit means that you want the OS to hang on to the executable image (in memory or in swap space) even when no users are running it. This is useful for programs (like the C compiler) are executed frequently, but that often don't overlap between one run and the next. In most environments setting this on fglgo wouldn't help you much. (At least this is how it was when _I_ learned Unix; sometimes they change things on me ;-() -- Harry Bochner bochner@das.harvard.edu