Hello, Peter Baumgarten, le Tue 11 Mar 2014 02:44:36 -0500, a écrit : > I'm trying to be a hurd developer by jumping straight in and trying to > tackle a bug.
Good! > This may not be a hurd bug, but I only see it with the > hurd version of sudo. It is a hurd bug. > I am trying to figure out why I get this message > "visudo: /etc/sudoers busy, try again later" when I run visudo as root. > I suspect something has a file lock on /etc/sudoers. No, it's rather the locking function which spuriously fails. The debian/patches/use-flock-on-hurd.diff patch is supposed to make sudo use flock instead of lockf, but that doesn't seem to actually happen. Some autoconf patching is probably needed there to fix things. Another way is to just fix lockf in glibc (for now it is just returning ENOSYS), it seems sudo simply locks the whole file, so it would be the simple case to implement. Samuel