Prior to mu sourcing .profile, those commands showed nothing. Once I ran . .profile, I get what I expected: larry@hammerhead:~$ which killsol.sh /home/larry/bin/killsol.sh larry@hammerhead:~$ type killsol.sh killsol.sh is /home/larry/bin/killsol.sh larry@hammerhead:~$ so the question really comes down to why is .profile not being run on login (I already said I do not have the two files which might prevent it). This is Ubuntu 12.04 BTW. On Thu, Feb 27, 2014 at 6:50 AM, wrote: > Pls show the output of: > which foo.sh > or > type foo.sh > ET > > > Dazed_75 writes: > >> I thought $PATH contained the series of paths searched to find an >> executable file by the name specified on the command line. Specifically >> if >> my $ENV contains a $PATH which reads: >> /home/larry/bin: >> that an executable file like foo.sh found in /home/larry/bin/ could be run >> by simply typing foo.sh on the command line. What am I doing wrong as it >> does not work though it does if I type ./bin/foo.sh while in >> /home/larry/? >> -- >> Dazed_75 a.k.a. Larry >> Please protect my address like I protect yours. When sending messages to >> multiple recipients, use the BCC: (Blind carbon copy). Remove addresses >> from a forwarded message body before clicking Send. >> > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org > To subscribe, unsubscribe, or to change your mail settings: > http://lists.phxlinux.org/mailman/listinfo/plug-discuss > -- Dazed_75 a.k.a. Larry Please protect my address like I protect yours. When sending messages to multiple recipients, use the BCC: (Blind carbon copy). Remove addresses from a forwarded message body before clicking Send.