mir/sudo
2
0
Fork 0
mirror of https://github.com/sudo-project/sudo.git synced 2025-09-03 15:55:40 +00:00
Code Issues Releases Wiki Activity

Ignore files ending in '~' in sudo.d (emacs backup files)

Browse Source
This commit is contained in:
Todd C. Miller
2009-04-19 13:01:20 +00:00
parent 72a1d82412
commit 0509ce3f66
1 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
sudoers.pod
View File

@@ -477,15 +477,16 @@ into as part of package installation. For example, given:
#includedir /etc/sudoers.d #includedir /etc/sudoers.d
B<sudo> will read each file in F</etc/sudoers.d>, skipping files B<sudo> will read each file in F</etc/sudoers.d>, skipping file
that contain a C<.> character to avoid causing problems with package names that end in C<~> or contain a C<.> character to avoid causing
manager, B<visudo> or editor temporary files. Files are parsed in problems with package manager or editor temporary/backup files.
sorted lexical order. That is, F</etc/sudoers.d/01_first> will be Files are parsed in sorted lexical order. That is,
parsed before F</etc/sudoers.d/10_second>. Be aware that because F</etc/sudoers.d/01_first> will be parsed before
the sorting is lexical, not numeric, F</etc/sudoers.d/1_whoops> F</etc/sudoers.d/10_second>. Be aware that because the sorting is
would be loaded B<after> F</etc/sudoers.d/10_second>. Using a lexical, not numeric, F</etc/sudoers.d/1_whoops> would be loaded
consistent number of leading zeroes in the file names can be used B<after> F</etc/sudoers.d/10_second>. Using a consistent number
to avoid such problems. of leading zeroes in the file names can be used to avoid such
problems.
Note that unlike files included via C<#include>, B<visudo> will not Note that unlike files included via C<#include>, B<visudo> will not
edit the files in a C<#includedir> directory unless one of them edit the files in a C<#includedir> directory unless one of them