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..
signature.asc
Description: This is a digitally signed message part
