Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: comp.unix.wizards
Subject: Re: umask under 4.3 BSD
Message-ID: <7430@elsie.UUCP>
Date: Mon, 8-Jun-87 14:10:00 EDT
Article-I.D.: elsie.7430
Posted: Mon Jun  8 14:10:00 1987
Date-Received: Thu, 11-Jun-87 03:28:30 EDT
References: <7700@brl-adm.ARPA> <20397@sun.uucp>
Organization: NIH-LEC, Bethesda, MD
Lines: 22
Summary: A bug is born

> > Oh, by the way, I haven't checked it out yet myself, but someone
> > said that 4.3 login.c doesn't have a umask call in it.  What's to stop
> > one from adding it!
> 
> Nothing stops you from adding it; it was presumably removed because
> 4.3BSD sets the "umask" of process 0 to 022 (or whatever CMASK was
> set to when you built your system).

And thus was a bug born.  Everything is fine if you tye control-D at the
end of a terminal session:  init starts up a new copy of getty on the line,
with init's "umask" value (as determined by CMASK) passed on to getty;
getty eventually in turn passes that value on to login.

But if you end a terminal session by using a shell's built-in

	$ login

command, then login is executed directly and inherits whatever "umask" value
happened to be in effect at the time you used the built-in.
-- 
	UUCP: ..seismo!elsie!ado	   ARPA: elsie!ado@seismo.CSS.GOV
	     Elsie and Ado are trademarks of Borden, Inc. and Ampex.