At 2003-02-25T17:36:34Z, Matthew Seaman <[EMAIL PROTECTED]> writes: > The problem is the getlogin(2) call. getlogin(2) tells you who the > current user logged in as, which, given intervening calls to functions > like setruid(3), setuid(2) or seteuid(2) is not necessarily the same thing > as the uid running the process.
Actually, the problem I was encountering turned out to be even more
annoying, involving some subtle interaction between mod_perl, Apache, and
rcs. Apparently rcs looks at $LOGNAME to determine what user to lock files
as. Since that variable wasn't explicitly set anywhere in Apache's
environment, rcs decided to go with getlogin() or similar. The solution was
to export $ENV{'LOGNAME'} = 'www', as per:
http://twiki.org/cgi-bin/view/Codev/RcsNonStrictLocking
--
Kirk Strauser
In Googlis non est, ergo non est.
pgp00000.pgp
Description: PGP signature
