Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrlnk!ncrwic!wbcs!jwf
From: jwf@wbcs.UUCP (John W. Flaherty)
Newsgroups: comp.sys.apollo
Subject: Re: rlogin not switching to user's home directory
Summary: /bin/start_??
Keywords: rlogin home directory tcp
Message-ID: <103@wbcs.UUCP>
Date: 2 Aug 88 20:27:12 GMT
References: <591@mailrus.cc.umich.edu> <3d85b2bc.10b48@apollo.COM> <1761@imagen.UUCP>
Organization: Boeing Computer Services, Wichita KS
Lines: 30

In article <1761@imagen.UUCP>, geof@imagen.UUCP (Geoffrey Cooper) writes:
> 
> I just tried it.  Setting the last field of /etc/passwd to
> /bin/start_csh, /bsd4.2/bin/start_csh both end up with the bourne shell
> getting executed.  DN3000 running 9.7.1.
> 
> - Geof Cooper


  A couple months ago, I also noticed the same problem.  With a little looking
  around I found:

    /bin/start_csh  and /bin/start_sh   (BSD) are links to the same file.
    Hmm.
    I created a link called /bin/start_ls,  guess what? it does an ls.
    This makes it obvious that the above program parses through argv[0]
    to figure out what to do. 
    
    I suspect that if there is no argv[0] then /bin/sh is started
    and that when the rlogin fires up the shell it isn't loading argv[0].

    execv(shell,NULL);

NOTE  We were at 9.5 at the time.  We now are at 9.7 and I haven't tried 
      it again.
    
-- 

John Flaherty  
UUCP: ..!ncrwic!wbcs!jwf 
  OR: ..!bcsfse!wbcs!jwf