> This raises an interesting issue.  Unless SETUIDSCRIPTS is set for the
> kernel, setuid scripts don't setuid at all.  There are good reasons for
> this but it seems a major deviation from common Unix to be undocumented
> (the code comments don't mention this, no man page does, it doesn't
> even show up in ALL (maybe should be LOTS anyways...it's certainly not
> ALL)).

umm, i can't quite parse this...

"it seems a major deviation from common Unix" -- what is "it"?
SETUIDSCRIPTS? or the fact that setuid scripts don't setuid at all?

the former probably should be documented, but i'd really rather that
anybody who wants to use it have to look over the code, anyway.

the latter is 100% standard UN*X -- normally, the set-id bits for
scripts are ignored, because (since most un*xes don't have /dev/fd/*)
there's no safe way to do set-id scripts.



chris

------------------------------------------------------------------------------