Re: Expected bahaviour of os.chroot and os.getcwd

2010-09-14 Thread r0g
On 14/09/10 11:19, Nobody wrote: On Mon, 13 Sep 2010 19:04:53 +0100, r0g wrote: i.e. So do I always have to change directory after changing into a chroot? You don't *have* to change the directory, but not doing so probably defeats the point of performing a chroot(). Thanks for the info 'No

Re: Expected bahaviour of os.chroot and os.getcwd

2010-09-14 Thread Nobody
On Mon, 13 Sep 2010 19:04:53 +0100, r0g wrote: > i.e. So do I always have to change directory after changing into a chroot? You don't *have* to change the directory, but not doing so probably defeats the point of performing a chroot(). > The reason I ask is because an app I was running inside th

Re: Expected bahaviour of os.chroot and os.getcwd

2010-09-13 Thread Lawrence D'Oliveiro
In message , r0g wrote: > i.e. So do I always have to change directory after changing into a chroot? When all else fails, read the man page . -- http://mail.python.org/mailman/listinfo/python-list

Re: Expected bahaviour of os.chroot and os.getcwd

2010-09-13 Thread Ian Kelly
On Mon, Sep 13, 2010 at 12:04 PM, r0g wrote: > i.e. So do I always have to change directory after changing into a chroot? > Yes, as documented in the man page for the chroot system call: This call changes an ingredient in the pathname resolution process and does > nothing else. > > This call do

Expected bahaviour of os.chroot and os.getcwd

2010-09-13 Thread r0g
Hi CLP! Not been here for ages, I hope everyone is doing well :) I just want to check if this is the intended behaviour (2.2 to 2.7)... import os print os.getcwd() os.chroot("/home/r0g/whatever/") print os.getcwd() os.chdir("/") print os.getcwd() /home/r0g/AAA_BACKED_UP/Code/py /home/r0g/AA