Bug#607823: cvsd: notice for chroot not working with nodev on partition /var
2010/12/23 Arthur de Jong adej...@debian.org: On Thu, 2010-12-23 at 11:07 +0200, Teodor MICU wrote: 2010/12/22 Arthur de Jong adej...@debian.org: 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. You mean that cvsd-buildroot did not complain? Note that cvsd-buginfo also contains a prominent notice about the mount options. I didn't notice at that time and looking back at the install journal I've found that it does: | [..] | installing libraries... done. | creating /var/lib/cvsd/dev devices... FAILED (unable to use devices) However, the 'cvsd' server didn't complain at runtime but only the cvs client. I have no idea how the client gets to know that could not open /dev/null but the server doesn't. 'cvsd-buginfo' didn't complain because I've already moved /var/lib/cvsd to /srv where there is no nodev mount option. Perhaps that could be added to the FAQ or README. Yes, that was my suggestion for this bug report. I've added an entry to the FAQ. Great. This means you can close this bug report once you upload the next version with this documentation update. 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. Since I've got more questions about this from people who haven't read the FAQ and this does not provide much extra debugging info, I've removed the log message. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607823: cvsd: notice for chroot not working with nodev on partition /var
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
Bug#607823: cvsd: notice for chroot not working with nodev on partition /var
On Thu, 2010-12-23 at 11:07 +0200, Teodor MICU wrote: 2010/12/22 Arthur de Jong adej...@debian.org: 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. You mean that cvsd-buildroot did not complain? Note that cvsd-buginfo also contains a prominent notice about the mount options. 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. 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. cvsd-passwd should do what is most logical depending on the contents of cvsd.conf. The format of CVSROOT/passwd is described in the FAQ but it you have anything that should be added, improvements are welcome. Perhaps that could be added to the FAQ or README. Yes, that was my suggestion for this bug report. I've added an entry to the FAQ. 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. Since I've got more questions about this from people who haven't read the FAQ and this does not provide much extra debugging info, I've removed the log message. Thanks for your feedback. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#607823: cvsd: notice for chroot not working with nodev on partition /var
Package: cvsd Version: 1.0.21 Severity: wishlist Hi, 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; - couldn't checkout due to missing :cvsd$ for all accounts on CVSROOT/passwd. Although the second item is documented in README.gz for a new repo, the first issue is not mentioned at all. 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? Thanks -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers squeeze-updates APT policy: (600, 'squeeze-updates'), (600, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cvsd depends on: ii adduser 3.112+nmu2 add and remove users and groups ii cvs 1:1.12.13-12 Concurrent Versions System ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii lsb-base3.2-23.1 Linux Standard Base 3.2 init scrip cvsd recommends no packages. Versions of packages cvsd suggests: ii perl 5.10.1-16 Larry Wall's Practical Extraction pn tmpreaper none (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607823: cvsd: notice for chroot not working with nodev on partition /var
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. - 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$. 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. 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). Thanks for your feedback. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
