[lkml]   [2001]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: umask 000 bug/difference
On Friday July 13, wrote:
> The 2.4.x kernels starting with 2.4.3 (i think) have, after
> load, left a umask of 0000.

That was me. nfsd started to use "daemonize" so it shared the umask
(and rest of current->fs, and other stuff) with init, so we changed
the default umask to 0 as knfsd didn't want any umask getting in the

It seems that someone at Redhat changed their init so that it set the
umask back to 0022, and this affected nfsd badly.

Linus has just accepted a patch which makes nfsd completely
independant of the umask setting, and sets the default umask back to
0022. You should see it in 2.4.7-pre7

For more info, look for the thread in linux-kernel with
[PATCH] Bug in NFS
in the subject.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:57    [W:0.035 / U:0.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site