On Mon, May 28, 2012 at 09:37:59AM +0200, Joachim Breitner wrote: > on my laptop, I sometimes have a long running schroot session (several > days). It seems that schroot is only copying the current > /etc/resolv.conf when I begin the session, or when it is recovered at > boot time, but not everytime I enter it. This causes problems when I > move locations between uses of the session. It also causes problems when > the schroot init script runs before the network is set up, as it will > copy an empty /etc/resolv.conf. > > It seems that this could be fixed if always the current /etc/resolv.conf > is used.
Hi Joachim, We used to have "exec" scripts in addition to "setup" scripts, which were run once per command being run, rather than once per session. These lived in /etc/schroot/exec.d rather than /etc/schroot/setup.d. These were never used for any practical purpose, so they were removed some years back. However, we could certainly add them back to make this possible. Should anything else be updated as well? While it's possible to update NSS databases etc., these can be potentially expensive operations, while copy resolv.conf is not. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org