Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!ames!pasteur!ucbvax!decwrl!hplabs!hpda!hpcuhb!hpcllla!hpclisp!hpclscu!shankar
From: shankar@hpclscu.HP.COM (Shankar Unni)
Newsgroups: comp.unix.wizards
Subject: Re: Re: ksh weird files
Message-ID: <670018@hpclscu.HP.COM>
Date: 8 Jun 88 21:41:27 GMT
References: <5658@chinet.UUCP>
Organization: HP NSG/ISD Computer Language Lab
Lines: 14

>................................................................ But I've some
>other questions. How do you get a sh script running at login (the password
>file entry should be an executable I thought). When login or getty or whoever
>goes to exec the sh script, how does it know which command interpreter to use
>(I don't think it knows of #! lines, in fact it doesn't even know the c.i.
>issue) ?

No, you *can* specify shell scripts as login shells. The code to handle non-
executables is in exec(2), and it works just fine whether it's called from the
shell or from getty. It's usually a good idea to put a #! line at the top,
just to be sure what shell gets run. 

--
Shankar Unni.