ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

note that umask is not set by the BIND 9 named [RT #1093]

Browse Source
This commit is contained in:
Andreas Gustafsson
2001-06-28 23:28:34 +00:00
parent 9a72459b60
commit 562c601b21
1 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/misc/migration
View File

@@ -218,4 +218,14 @@ directing queries for a given domain to a particular set of name
servers.
$Id: migration,v 1.36 2001/06/11 20:46:15 gson Exp $
7. Umask not Modified
The BIND 8 named unconditionally sets the umask to 022. BIND 9 does
not; the umask inherited from the parent process remains in effect.
This may cause files created by named, such as journal files, to be
created with different file permissions than they did in BIND 8. If
necessary, the umask should be set explicitly in the script used to
start the named process.
$Id: migration,v 1.37 2001/06/28 23:28:34 gson Exp $