[cod] Semi off topic: COD rentals
Dali -[OBI]-
dali at axelero.hu
Mon Sep 27 11:46:10 EDT 2004
I read it in chmod manual:
"STICKY FILES
On older Unix systems, the sticky bit caused executable files to
be
hoarded in swap space. This feature is not useful on modern VM
sys-
tems, and the >> Linux kernel ignores the sticky bit on files. <<
Other ker-
nels may use the sticky bit on files for system-defined purposes.
On
some systems, only the superuser can set the sticky bit on files."
What is the truth then?
----- Original Message -----
From: Mark J. DeFilippis
To: cod at icculus.org
Sent: Sunday, September 26, 2004 2:41 AM
Subject: RE: [cod] Semi off topic: COD rentals
If you are executing the same executable and can use parameters on the
command line that is
fine. It is the same inode. The question I was answering was for a person
who appeared to
not understand why, if Linux is in fact a multiuser/multi-tasking OS, what
difference does
it make if I load from one file or many copies of the file.
In the scenario you present... if you are executing the same file, it is the
same
inode. Make it sticky... and you have the same as the symlink scenario.
For those admins that wish to have a separate executable in the user
space (on perhaps a server where the admin choose to have the executable
in the users space with his other files and configs) the symlink method
works
very well.
If your servers are being spawned by calling the same executable, you in
fact
are correct, you get the same benefits. For added savings on load, make the
executable
sticky, and your golden.
Dr. D
More information about the Cod
mailing list