[olug] Fwd: Re: umask 000 bug/difference

[Phil Brutsche]

Saw this on the kernel developer's list a little while ago and thought
some people might be interested...

----- Forwarded message from Neil Brown <neilb at cse.unsw.edu.au> -----
Date: Sat, 14 Jul 2001 14:53:54 +1000 (EST)
From: Neil Brown <neilb at cse.unsw.edu.au>
Reply-To: Neil Brown <neilb at cse.unsw.edu.au>
Subject: Re: umask 000 bug/difference
To: josh at pulltheplug.com

On Friday July 13, josh at pulltheplug.com 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
way.

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.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


----- End forwarded message -----




Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: olug-unsubscribe at bstc.net
For additional commands, e-mail: olug-help at bstc.net