[Buildd-tools-devel] schroot question

[Roger Leigh]

On Mon, Feb 02, 2009 at 07:56:43AM -0500, Steven Hirsch wrote:
> On Fri, 30 Jan 2009, Roger Leigh wrote:
>
>>> The folks on the autofs mailing list want debugging output from the
>>> daemon under failing conditions.  What is the most expedient way to
>>> enable system logging within schroot?
>>
>> If it's logging via the standard syslog facility, then simply ensuring
>> the presence of /dev/log inside the chroot should be sufficient.
>
> I was able to get logging operational and at least one of my problems is  
> due to the automounter receiving a SIGUSR2 just after startup!  I cannot  
> find any place in the schroot code base where this could be coming from.  
> Does it ring any bells with you?

No.  We never send that signal to a child process.  The only signals
we ever send are SIGTERM and SIGKILL (in the 15killprocs setup script),
and this is only run when ending a session.

> In the case where I establish the shell in a local directory and cd into  
> the automount hierarchy, things work ok. When I attempt to go directly  
> into the automount area (e.g. 'schroot -d /net/home/... ') it's seeing 
> the SIGUSR2 and exiting.  Very strange.

I'm not sure if there's a way to trace which process sent the signal.
You could try strace -f -ff -o log (to trace all schroot child processes).

> I cannot seem to get a straight answer out of anyone on the autofs list  
> regarding the apparent need to run a second daemon inside the chroot.  
> The core developer lists can be VERY insular if they detect someone not 
> deemed to be an Alpha Geek :-).  I'm just "supposed to know.." how the 
> VFS deals with this sort of thing, I guess.

That's unfortunate.  Perhaps they aren't sure themselves ;-)
You could also try going via the Debian autofs maintainer, or the
linux-kernel mailing list.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.