Addition, that's what happens trying to close any of the open sessions:
$ schroot -c
session:sid-amd64-sbuild-d6d9a259-3c44-46b1-9814-8b404cac5c6b -e -f
E: 15binfmt: update-binfmts: unable to open
/var/lib/schroot/mount/sid-amd64-sbuild-d6d9a259-3c44-46b1-9814-8b404cac5c6b/bin/sh:
No such fil
On 10/9/13, Roger Leigh wrote:
> On Mon, Oct 07, 2013 at 12:38:04PM -0400, shawn wilson wrote:
>> This is at the top of every config file, but I can't find it documented:
>>
>> . "$SETUP_DATA_DIR/common-data"
>> . "$SETUP_DATA_DIR/common-functions"
>> . "$SETUP_DATA_DIR/common-config"
>>
>> Where
On Mon, Oct 07, 2013 at 12:38:04PM -0400, shawn wilson wrote:
> This is at the top of every config file, but I can't find it documented:
>
> . "$SETUP_DATA_DIR/common-data"
> . "$SETUP_DATA_DIR/common-functions"
> . "$SETUP_DATA_DIR/common-config"
>
> Where is this being sourced from (ie, where i
On Mon, Oct 7, 2013 at 2:20 PM, wrote:
> Le 07.10.2013 19:50, shawn wilson a écrit :
>
>> Not a bad idea. However:
>> find / -type f -print0 | xargs -0 -i{} -P 10 grep -H 'SETUP_DATA_DIR='
>> {} 2> /dev/null
>>
>> found nothing.
Just to be complete (so that maybe this shows up on google when the
Le 07.10.2013 19:50, shawn wilson a écrit :
Not a bad idea. However:
find / -type f -print0 | xargs -0 -i{} -P 10 grep -H
'SETUP_DATA_DIR='
{} 2> /dev/null
found nothing.
On Mon, Oct 7, 2013 at 1:05 PM,
wrote:
Le 07.10.2013 18:59, Shawn Wilson a écrit :
berenger.mo...@neutralite.org wro
Le 07.10.2013 18:59, Shawn Wilson a écrit :
berenger.mo...@neutralite.org wrote:
Le 07.10.2013 18:38, shawn wilson a écrit :
This is at the top of every config file, but I can't find it
documented:
. "$SETUP_DATA_DIR/common-data"
. "$SETUP_DATA_DIR/common-functions"
. "$SETUP_DATA_DIR/common
berenger.mo...@neutralite.org wrote:
>
>
>Le 07.10.2013 18:38, shawn wilson a écrit :
>> This is at the top of every config file, but I can't find it
>> documented:
>>
>> . "$SETUP_DATA_DIR/common-data"
>> . "$SETUP_DATA_DIR/common-functions"
>> . "$SETUP_DATA_DIR/common-config"
>>
>> Where is t
Le 07.10.2013 18:38, shawn wilson a écrit :
This is at the top of every config file, but I can't find it
documented:
. "$SETUP_DATA_DIR/common-data"
. "$SETUP_DATA_DIR/common-functions"
. "$SETUP_DATA_DIR/common-config"
Where is this being sourced from (ie, where is the 'common-data'
file?)
On Tue, Feb 16, 2010 at 08:27:48AM +, arenev...@fdn.fr wrote:
> Andrew Malcolmson wrote:
>
> > Also, I think your 'directory'
> > setting should be 'location', i.e. 'location=/srv/chroot/ia32'. See
> > man schroot.conf for details.
>
> actually, location seems to be deprecated, while direct
Andrew Malcolmson wrote:
> On Mon, Feb 15, 2010 at 8:15 AM, wrote:
>>
>> Here is my schroot.conf
>>
>> [ia32]
>> description=Debian testing 32bits
>> directory=/srv/chroot/ia32
>> users=arno
>> root-groups=root
>> root-users=arno
>> run-exec-scripts=true
>>
>
> You've omitted the 'type=' settin
On Mon, Feb 15, 2010 at 8:15 AM, wrote:
>
> Here is my schroot.conf
>
> [ia32]
> description=Debian testing 32bits
> directory=/srv/chroot/ia32
> users=arno
> root-groups=root
> root-users=arno
> run-exec-scripts=true
>
You've omitted the 'type=' setting which causes the type to default to
'plai
shame <[EMAIL PROTECTED]> writes:
> Did you find a satisfactory solution to this problem?
> I also have the nasty build up of sessions using schroot.
>
> Using schroot -e --all-sessions does clear out the sessions but I
> can't find a way to automate this.
It's worth mentioning that the latest sc
Did you find a satisfactory solution to this problem?
I also have the nasty build up of sessions using schroot.
Using schroot -e --all-sessions does clear out the sessions but I can't find a
way to automate this.
I tried adding this to a launcher on my panel ([i]schroot -e --all-sessions &&
dc
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've only done this setting up a chroot to run 32bit applications on a
64bit system but it should be equally applicable to your situation.
this is exactly my situation. so far i was using permanent bindmounts in
the /etc/fstab file, as described in the amd64 howto
Please note that if yo
On (10/11/06 09:53), Lubos Vrbka wrote:
> could anybody please show me how to setup schroot so, that it
> automatically bindmounts the /dev, /tmp and /home directories inside the
> chroot when it is entered? until now i was using permanent bind mount in
> my fstab. however, having the directorie
20 matches
Mail list logo
