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
