Anton Piatek wrote:
Wackojacko wrote:
Anton Piatek wrote:
Wackojacko wrote:
Anton Piatek wrote:
It may help if you could give us more information on what myprogram
does, and how it is launched, in the chroot?
In any case you could try
#schroot -e --all-sessions
to kill the existing processes
Wackojacko wrote:
> Anton Piatek wrote:
>> Wackojacko wrote:
>>> Anton Piatek wrote:
Hi, I set up a basic schroot environment to run a couple of 32 bit
apps on my amd64 box. The problem is that when the program exits
schroot leaves all its session data behind, mount points and all (s
Anton Piatek wrote:
Wackojacko wrote:
Anton Piatek wrote:
Hi, I set up a basic schroot environment to run a couple of 32 bit
apps on my amd64 box. The problem is that when the program exits
schroot leaves all its session data behind, mount points and all (so
`mount` returns a hell of a lot of e
Wackojacko wrote:
> Anton Piatek wrote:
>> Hi, I set up a basic schroot environment to run a couple of 32 bit
>> apps on my amd64 box. The problem is that when the program exits
>> schroot leaves all its session data behind, mount points and all (so
>> `mount` returns a hell of a lot of entries)
>>
Anton Piatek wrote:
Hi,
I set up a basic schroot environment to run a couple of 32 bit apps on my
amd64 box. The problem is that when the program exits schroot leaves all its
session data behind, mount points and all (so `mount` returns a hell of a lot
of entries)
schroot is being called as
Hi,
I set up a basic schroot environment to run a couple of 32 bit apps on my
amd64 box. The problem is that when the program exits schroot leaves all its
session data behind, mount points and all (so `mount` returns a hell of a lot
of entries)
schroot is being called as follows
`ls -l myprogr
6 matches
Mail list logo
