On Wed, Feb 4, 2009 at 9:12 AM, Timo Sirainen <t...@iki.fi> wrote: > On Wed, 2009-02-04 at 07:42 +1300, Michael Kerrisk wrote: >> > To prevent other people from wasting their time with fexecve(), I suggest >> > adding something like this to the description: >> > >> > Linux implements fexecve() by executing the binary via proc filesystem, >> > so /proc needs to be mounted and available during the fexecve() call. >> >> I can see some merit in adding a sentence like this, but: >> >> > And for ERRORS: >> > >> > ENOENT: /proc filesystem not available. >> > >> > ref: http://lkml.org/lkml/2006/12/27/140 >> >> surely the error is ENOSYS (see the glibc source), which is already >> documented in the man page? > > Well, what I did was: > > 1. open() an executable > 2. chroot() to empty directory > 3. drop root privileges > 4. fexecve() > > And fexecve() return ENOENT. So I was assuming it's because there was > no /proc in the empty dir..
Can you provide a very simple test program? In my tests, I am seeing ENOSYS, as I would expect from reading the source.` -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
