reopen 378469
found 378469 0.99.3-1
tags 378469 + confirmed patch fixed-upstream pending
thanks
Matthew Foulkes <[EMAIL PROTECTED]> writes:
> The trace.log file produced by running
>
> $ strace -o trace.log schroot -c ia32 -p oowriter
>
> is attached. I did not know how to trace a version of sc
Dear Roger,
The trace.log file produced by running
$ strace -o trace.log schroot -c ia32 -p oowriter
is attached. I did not know how to trace a version of schroot running in the
background (adding an ampersand to the command above would presumably put
strace into the background, not schroot) a
Matthew Foulkes <[EMAIL PROTECTED]> writes:
> I looked at the source but am not expert enough to investigate this
> myself. Sorry.
No problem. To further investigate it, I would very much like to see
the strace output, if you could run that for me.
strace -o trace.log schroot
Since the prog
I looked at the source but am not expert enough to investigate this
myself. Sorry.
The ideal behaviour, in my view, would be for
schroot -c ia32 -p any_program &
to be equivalent to logging in to the chroot, changing to the right
working directory, running
any_program &
and then logging
[Please can you keep the [EMAIL PROTECTED] in the Cc:, so it gets
recorded in the bug history. Thanks.]
Matthew Foulkes <[EMAIL PROTECTED]> writes:
> Dear Roger,
>
> On Mon, Jul 17, 2006 at 11:00:56AM +0100, Roger Leigh wrote:
>> I would suggest either
>>
>> schroot -c ia32 -p oowriter >/dev/
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* kill
6 matches
Mail list logo
