Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!sgi!shinobu!odin!schuman
From: schuman@sgi.com (Aaron Schuman)
Newsgroups: comp.sys.sgi
Subject: Re: rsh (remote shell) -- undocumented(?) feature(?)
Keywords: umask
Message-ID: <1990Aug29.014812.14956@odin.corp.sgi.com>
Date: 29 Aug 90 01:48:12 GMT
References: <1406@contex.UUCP>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics 415-335-1901
Lines: 8

I just looked over the source for rshd, and I didn't see it setting
umask anywhere.  It isn't set in rcmd(3) either.  Doing a setuid
system call doesn't source the rc files belonging to the new user,
so umask isn't getting set that way.

The umask shell variable is inherited by child processes.  My guess
is that on your system rshd's parent (inetd) has a umask of 022,
and so does rshd's grandparent (init).