set effective user to root 1571
Mike - EMAIL IGNORED
Nope. The sticky-bit is "chmod o+tfoo-bar".
chmod u+sfoo-bar is the "set-user-id" bit and chmod g+sfoo-bar is the "set-group-id" bit... these makes the process to run with the priviliges of the *files* owner and-or group -- rather than with the priviliges of the user that invoked it.
IF the program can only alter one single file, that is much better. The way I read your request was...
The "sticky-bit" (o+t) is no longer used for execuatbles in linux (support removed); but once upon a time, executables with their sticky-bits set, would remain constantly in the swap-space (swap-parbreastion or-file), thus saving the time of loading the program from disk and get it started-up for each subsequent invocation. Only root could set this.
On Tue, 06 Jun 2006 00:55:54 +0000, Unruh I wonder how one should judge your...
However, any user may set the sticky-bit on one of their own directories. This is usually done in combination with allowing write access to all users on that directory (chomd o+w). Allowing all users to write to a directory, will sooner or later result in users overwriting eachoters files. Setting the sticky-bit, will prevent other users than the owner of the file (and the owner of the directory) from overwriting-deleting that file.
A typical example aretmp andvar-tmp; all users may write to this directory, but thanks to the sticky-bit, they can only delete-overwrite their own files.
man chmod info chmod
-Koppe