[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Re: svn behavior in chroot-environments

From: Mathias Gumz <mathias.gumz_at_gmail.com>
Date: 2004-07-09 04:21:14 CEST

(ok, lets rephrase this whole thread not as bug but as strange
behavior in the meaning of "i am not sure whats going on inside
subversion at this level" :)

the whole problem seems to be the missing passwd-database. as a trace
in obsd shows:

24040 svn NAMI "/etc/spwd.db"
24040 svn RET open -1 errno 2 No such file or directory
24040 svn CALL open(0x2fb84da9,0,0)
24040 svn NAMI "/etc/pwd.db"
24040 svn RET open -1 errno 2 No such file or directory

it wants to access /etc/spwd.db and/or /etc/pwd.db. man getpwuid also
lists /etc/passwd as a passwd-database-file but as i can see in my
test-program getpwuid doesnt touch /etc/passwd. if one of the both
files does exist inside the chroot svn would never prompt for a
username.

so, final conclusion (for now?)

websvn should call svn with the --non-interactive flag because its not
really interactive and one doesnt need to provide /etc/pwd.db or
/etc/spwd.db inside the chroot, even if it would be faked. its not a
"bug" in subversion.

regards and thanks so far,
  mathias

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 9 04:21:48 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.