Your message dated Mon, 17 Jul 2006 11:00:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line [Buildd-tools-devel] Bug#378469: backgrounded schroot
processes do not terminate
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: schroot
Version: 0.99.3-1
Severity: minor
I use schroot to run 32-bit programs such as openoffice on an
AMD64 system. Commands such as
$ schroot -c ia32 -p oowriter
work fine. But if the command is backgrounded
$ schroot -c ia32 -p oowriter &
the schroot process is *not* killed when oowriter exits:
$ jobs
[1]+ Stopped schroot -c ia32 -p oowriter
It is necessary to kill these stopped processes explicitly to
get rid of them, which is a little annoying.
My schroot.conf file is:
[ia32]
description=Debian unstable (32 bit)
location=/var/chroot/sid-ia32
priority=3
groups=users
personality=linux32
On a separate issue, the DESCRIPTION section of the schroot man page
discusses the -d option, which does not seem to exist.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.6
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages schroot depends on:
ii libboost-program-options1.33. 1.33.1-4 program options library for C++
ii libboost-regex1.33.1 1.33.1-4 regular expression library for C++
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libgcc1 1:4.1.1-8 GCC support library
ii liblockdev1 1.0.3-1 Run-time shared library for lockin
ii libpam0g 0.79-3.1 Pluggable Authentication Modules l
ii libstdc++6 4.1.1-8 The GNU Standard C++ Library v3
ii libuuid1 1.39-1 universally unique id library
schroot recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.99.3-1
Matthew Foulkes <[EMAIL PROTECTED]> writes:
>> > the schroot process is *not* killed when oowriter exits:
>> >
>> > $ jobs
>> > [1]+ Stopped schroot -c ia32 -p oowriter
>>
>> This, TTBOMK, is the correct behaviour, even though it's annoying.
>>
>> When you background schroot with &, the process is stopped. It was
>> stopped due to receiving SIGTTIN or SIGTTOU (strace will help here),
>> and the correct behaviour on receiving those signals is to be stopped
>> (this is handled completely automatically by the kernel). Both
>> schroot and the child process stop, because they are in the same
>> process group created by your shell; this is also correct.
>>
>> It doesn't stop if running a non-interactive process. I would
>> therefore suggest you find out why oowriter is trying I/O on the
>> controlling tty. Try redirecting stdin/stdout/stderr to /dev/null,
>> and see if this makes any difference.
>
> Thanks for your very clear explanation. I understand the behaviour now
> and agree that it is correct; if you ran, for example, "vi &", it is the
> behaviour you would want.
Agreed.
> You are also correct that oowriter is writing to the controlling tty --
> a message complaining that the en_US locale is not available. After
> work today I'll see if your /dev/null redirection trick works or whether
> I can convince openoffice.org to use the en_GB locale.
I would suggest either
schroot -c ia32 -p oowriter 2>&1 >/dev/null
or
schroot -c ia32 -p /bin/sh -c 'oowriter 2>&1 >/dev/null'
The first will redirect both the oowriter /and/ the schroot messages.
The second will redirect only the oowriter messages. If it's writing
only to stdout or only to stderr, you could modify the redirection to
just "2>/dev/null" or ">/dev/null", but I would only do that if you
need to care about error messages, which in this case you probably
don't.
> I am happy for you to close this non-bug.
Done.
If you run into any other problems, just let me know.
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 sign and encrypt your mail.
pgpbOe7vf8BLg.pgp
Description: PGP signature
--- End Message ---
