David Korn wrote:
>
> Subject: Re: [ast-users] Login shell starting in unreadable directory
> --------
>
> > Hi all,
> >
> > This is a strange case, but I think there's a bug in ksh startup when
> > a login shell is started in an unreadable directory. One example is
> > when using sudo to invoke a login shell from, say, the invoking user's
> > mode-700 homedir.
> I tried this and ran
> ksh --login
> from /tmp/unreadable.
>
> I did not observe any problems when I did this so it might depend on
> your ENV file.
It's very inconsistent... --login (which is not documented btw!) gives
slightly different results than perl -e 'exec { "/bin/ksh" } "-ksh"'.
It's the same idea though -- a loop that looks like this:
for file in ${ENVIRON_RC_DIRECTORY:-/foo/bar/rc.d}/*; do
. $file
done
is failing with an error like this:
/foo/ba: cannot open [No such file or directory]
So $file is getting truncated at a strange place. If I put an "echo
$file" above, it might truncate at a different place, or it might show
something like "/foo/bar/rc.d/file1 /fo" (i.e. overrun where its
value should end). I have a variety of reproducible cases for this,
but so far, nothing simple enough to replicate outside of our
environment.
I can also confirm the $PWD strangeness (looks like it's set to $HOME,
although pwd and /bin/pwd disagree) although I'm not sure if that's
contributing to the problem.
Back to my other question, which should be easier:
> > Also, in case nobody has any ideas... what incantation can I give to
> > "bin/package make" to get a -g build?
--
Ron Isaacson
Morgan Stanley
[email protected] / (212) 276-1349
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
