Josh Hurst wrote:
>
> Is there a reason why /etc/ksh.kshrc is not read if ksh93 is called 'sh'?
Good question... I guess the following expression is not true, causing
the |if()| to skip the profile code:
-- snip --
if(!sh_isoption(SH_NOUSRPROFILE) && !sh_isoption(SH_PRIVILEGED) &&
sh_isoption(SH_RC))
{
-- snip --
However I can't reproduce the problem - in my case /etc/ksh.kshrc is
read when I run ksh93 as "./sh" (e.g. executable named "./sh" ... I
didn't test this for /sbin/sh).
In general it may be better to have a seperate /etc/sh.shrc when the
shell is called "sh" since the default system shell (assuming ksh93 is
used as such (e.g. /usr/xpg4/bin/sh or /sbin/sh)) may have different
requirements for interactive sessions (and/or it may be a nice idea to
add something like /etc/sh.shrc+~/.shrc to the POSIX shell standard in
the future).
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
