Bugs item #303084, was changed at 2006-02-19 12:54 by Justus Winter You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=303084&group_id=30628
Status: Open Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: visudo problems Category: None Group: None Resolution: None Initial Comment: visudo says the sudoers file is busy, even if the machine had a fresh reboot. ---------------------------------------------------------------------- Comment By: Justus Winter (teythoon-guest) Date: 2010-05-06 20:29 Message: Yeah, lockf isn't implemented, but flock is and visudo can use either. They select the locking mechanism based on the target platform, here's a patch for configure.in: ~~~ snip ~~~ diff -r 91d8979bd32f configure.in --- a/configure.in Thu May 06 19:39:12 2010 +0200 +++ b/configure.in Thu May 06 19:40:22 2010 +0200 @@ -1706,6 +1706,9 @@ ;; *-gnu*) OSDEFS="${OSDEFS} -D_GNU_SOURCE" + # lockf() isn't implemented on the hurd -- use flock instead + ac_cv_func_lockf=no + ac_cv_func_flock=yes ;; esac ~~~ snip ~~~ With that patch I am able to visudo the sudoers file, but it segfaults when the editor exits. I can't debug this any further atm since gdb is broken on my debian installations... ---------------------------------------------------------------------- Comment By: Samuel Thibault (sthibault) Date: 2010-03-02 12:19 Message: IIRC the problem is that visudo uses record locking, which is not yet supported on GNU/Hurd. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=411594&aid=303084&group_id=30628 -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oa5pb-0003db...@alioth.debian.org