The file name comes from the ksh93 source at AT&T (upstream).
April
> Date: Tue, 17 Oct 2006 13:30:36 -0700
> From: John Plocher <john.plocher at sun.com>
> Subject: Re: /etc/ksh.kshrc for ksh93 [PSARC/2006/587 Timeout: 10/24/2006]
> Cc: Don Cragun <don.cragun at sun.com>,
ksh93-integration-discussion at opensolaris.org, PSARC-EXT at sac.sfbay.sun.com
> MIME-version: 1.0
> Content-transfer-encoding: 7BIT
> x_sac_archived: PSARC/2006/587
> x_sac_loop: roland.mainz at nrubsig.org april.chin at sun.com
ksh93-integration-discuss at opensolaris.org
> x_sac_info: auto-forwarded by the SAC mail system
> X-PMX-Version: 5.2.0.264296
> User-Agent: Mail/News 1.5.0.5 (X11/20060813)
>
> Nit: With this proposal, we will have the following shell config files
> living in /etc:
>
> /etc/profile
> /etc/suid_profile
> /etc/.login
> /etc/ksh.kshrc
> /etc/default/su
>
> Where does the name "ksh.kshrc" come from? I'm worried that we don't
> seem to have or be following any naming pattern for these shell startup
> files.
>
> -John
>
>
> login(1) says:
> For Bourne shell and Korn shell logins, the shell executes
> /etc/profile and $HOME/.profile, if it exists. For C shell
> logins, the shell executes /etc/.login, $HOME/.cshrc, and
> $HOME/.login. The default /etc/profile and /etc/.login files
> check quotas (see quota(1M)), print /etc/motd, and check for
> mail. None of the messages are printed if the file
> $HOME/.hushlogin exists. The name of the command inter-
> preter is set to - (dash), followed by the last component of
> the interpreter's path name, for example, -sh.
>
