Hi, 2010/12/22 Arthur de Jong <adej...@debian.org>: > On Wed, 2010-12-22 at 19:43 +0200, Teodor wrote: >> I've had three issues while setting up 'cvsd' with an existing repository: >> - no operation was working (i.e. cvs login) due to "nodev" mount option set >> for >> the /var partition where /var/lib/cvsd was located; > > Indeed, some devices need to be created inside the chroot jail and are > used by the cvs process. cvsd-buildroot should print a warning if the > created devices could not be used.
Right. The error was visible only to the client with an error message like "could not open /dev/null". >> - couldn't checkout due to missing ":cvsd$" for all accounts on >> CVSROOT/passwd. > > The formatting for CVSROOT/passwd files should be > cvsuser:passwordhash:cvsd > (assuming standard read-only setup). cvsd-passwd should set this up > correctly and both cvsd-buildroot and cvsd-buginfo should report most > configuration problems here. I don't know what you mean exactly by > ":cvsd$". Right, I was trying to say the same thing but shorter. All the accounts on the imported repository were "cvsuser:passwordhash:", meaning without the real system ID at the end ":cvsd". Indeed cvsd-passwd adds automatically the ":cvsd" entry even if not specified. >> Although the second item is documented in "README.gz" for a new repo, the >> first >> issue is not mentioned at all. > > Perhaps that could be added to the FAQ or README. Yes, that was my suggestion for this bug report. >> Also, I've put logging to "debug" and all operation (success or fail) will >> print >> this line on syslog: >> | cvsd[5740]: debug: select() failed (ignored): Interrupted system call >> >> Is this something to take into account? > > The above line can be safely ignored. It only means that the call to > select() was interrupted (probably due to the sub-process ending). The > cvs process that is started does provide very little debugging > information though and it is also hard to get extra info (see the FAQ > for details). Ok, though doesn't sound right for successful operations or it shouldn't be printed on any log level. > Thanks for your feedback. Welcome, thanks for your work. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
