Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh and login shells.
- X-seq: zsh-users 2145
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Timothy J Luoma <public+Lists/Unix/Zsh/Users@xxxxxxx>, "Larry P . Schrof" <schrof@xxxxxxxxxxx>
- Subject: Re: zsh and login shells.
- Date: Fri, 12 Feb 1999 23:14:54 -0800
- Cc: zsh-users@xxxxxxxxxxxxxx
- In-reply-to: <199902130246.VAA10174@ocalhost>
- Mailing-list: contact zsh-users-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199902122123.QAA05026@xxxxxxxxxxxxxxxxxx> <199902130246.VAA10174@ocalhost>
On Feb 12, 9:46pm, Timothy J Luoma wrote:
} Subject: Re: zsh and login shells.
}
} Author: "Larry P . Schrof" <schrof@xxxxxxxxxxx>
} Date: Fri, 12 Feb 1999 15:22:16 -0600
} ID: <199902122123.QAA05026@xxxxxxxxxxxxxxxxxx>
}
} > I know the system ksh was reading my old .login file before I
} > moved it out of the way and put in the (simple) new one.
Something just occurred to me that hadn't earlier:
As ksh doesn't normally read a file named .login (it uses .profile), it
must be the case that the system /etc/profile is reading .login with the
"." command. Is your .login writable by anyone other than yourself?
Perhaps /etc/profile tests that someone else couldn't have written into
your .login before it reads it?
} What would happen when zsh starts and processes .login ?
Zsh would only process .login if it were explicitly sourced. The usual
file for zsh is .zlogin ...
} Also, the condition should not be '-f', I would suggest something like this
}
} check that it IS executable
} and NOT a directory
} and NOT a link
and NOT writable by group/other ...
I'm not sure the "not a link" test is all that useful. If somebody could
put a link in his loc/bin directory, they could also replace the entire
executable.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author