chroot bug if arg not absolute path?

From: Dan Kegel (
Date: Thu Jul 03 2003 - 22:26:59 EST

On my Debian 3.0 system running the 2.4.18 kernel, I
ran into a funny problem: /usr/sbin/chroot, or the chroot()
system call followed by the chdir() system call,
seem to work if their argument is not an absolute path;
that is, scandir("/bin") can see the files in the jail,
but execlp("/bin/sh", "/bin/sh", 0) fails to find the /bin/sh
in the jail, and sets errno to ENOENT.

Is this a bug, or do I have a screw loose behind the wheel?
- Dan

Dan Kegel

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to More majordomo info at Please read the FAQ at

This archive was generated by hypermail 2b29 : Mon Jul 07 2003 - 22:00:22 EST