Wow, OK apologies for wasting everyone's time in that case but I have to say that its pretty confusing. Even within the sudoers file there are comments prefixed by a hash. But if your comment happens to start with #include it magically becomes active.
I now understand this is the intended behaviour, but in that case I'd humbly suggest that there should be another, better way of doing includes. Also, perhaps visudo should throw an error when it finds an #include that doesn't exist, rather than just exiting and then sudo refusing to do anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741398 Title: Commented line in sudoers file breaks sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1741398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
