On Wed, Jan 30, 2002 at 10:21:26AM -0700, Jon Arney wrote: > The upshot of the whole > thing is that if you call access() on a recursive link, > the /hurd/auth process goes nuts!
> I think this is a really neat feature of the 'access()' call and the > behavior of the /hurd/auth daemon, but not everyone sees things > the way I do :) It should definitely fail with ELOOP. > If you think it's appropriate, I'll try to track it further and > perhaps suggest a patch or something. Of course it's possible to > take the stance that "you shouldn't create recursive links" which > is fairly obvious, but accidents DO happen. The bug is probably in glibc/sysdeps/mach/hurd/access.c, which is the implementation of access() on the Hurd. That would be a good place to start your research. (Could also be in the file name lookup itself, or in the way it is used). Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
