[lkml]   [1996]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: chroot bug, & Re: Ideas for v2.1
: > This is  the normal behaviour,
: No it isn't.
: The man page for chroot on a SysV or BSD system states:
: chroot causes the given command to be executed relative to
: the new root. The meaning of any initial slashes (/) in the
: pathnames is changed for the command and any of its child
: processes to newroot. Furthermore, upon execution, the
: initial working directory is newroot.
: chroot(8) is broken if it doesn't leave you in newroot.

Hmmm, my FreeBSD man page says different:

chroot - change root directory
Dirname is the address of the pathname of a directory, terminated by an
ASCII NUL. Chroot() causes dirname to become the root directory, that
is, the starting point for path searches of pathnames beginning with `/'.

In order for a directory to become the root directory a process must have
execute (search) access for that directory.

It should be noted that chroot() has no effect on the process's current


 \ /
  Last update: 2005-03-22 13:37    [W:0.033 / U:3.356 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site