You only posted the output of which after sourcing .profile. Your
non-login, interactive bash sessions are sourcing .bashrc. Export your path
in there.
On Feb 27, 2014 5:29 PM, "Dazed_75" wrote:
> You guys need to read the thread which already shows the output of which
> and type. Let's just dro
You guys need to read the thread which already shows the output of which
and type. Let's just drop the whole subject as all we are getting is
repeats of the same questions.
On Thu, Feb 27, 2014 at 4:00 PM, KevinO wrote:
> On 02/27/2014 03:55 PM, Dazed_75 wrote:
> > Sean, as stated before, I do
On 02/27/2014 03:55 PM, Dazed_75 wrote:
> Sean, as stated before, I do have a bashrc and it is being adhered to by
> the system. There IS NO OUTPUT from killsol.sh. It is designed to kill a
> process if it exists and do so silently whether the process exists or not.
Larry,
Sean is asking for the
There is a utility called WHICH and you can use it by typing WHICH
KILLSOL.SH and it will give you some output. That is what I want! I don't
care about killsol's output. Just type "which killsol.sh"! Does your bashrc
set your path? Does your bashrc source any files in /etc?
On Feb 27, 2014 3:55 PM,
Sean, as stated before, I do have a bashrc and it is being adhered to by
the system. There IS NO OUTPUT from killsol.sh. It is designed to kill a
process if it exists and do so silently whether the process exists or not.
On Thu, Feb 27, 2014 at 3:52 PM, sean wrote:
> So, again, what is the ou
I usually put my junk in .bashrc and have .profile and .bash_profile run .
~/.bashrc
except for desktop stuff like my ssh-agent verification, which I put in the
interactive-only stuff.
On Thu, Feb 27, 2014 at 3:52 PM, sean wrote:
> So, again, what is the output of "which killsol.sh"? Also do y
So, again, what is the output of "which killsol.sh"? Also do you have a
.bashrc? If not try renaming your .profile to .bashrc.
On Feb 27, 2014 3:48 PM, "Dazed_75" wrote:
> Sean, when it is not working (I have not run .profile manually), it prints
> killsol.sh: command not found as expected. When
Sean, when it is not working (I have not run .profile manually), it prints
killsol.sh: command not found as expected. When I have run .profile
manually, it executes properly and the is no cli output as I designed.
james, i get /bin/bash as my shell
kitepilot, I get bash
On Thu, Feb 27, 2014 at
Or:
echo $0
ET
James Mcphee writes:
dash uses /etc/profile, ~/.profile, and $ENV (if available). grep your
username from /etc/passwd to find your shell.
On Thu, Feb 27, 2014 at 12:04 PM, sean wrote:
No, we want the output of :
which killsol.sh
"which" tells you where "killsol.sh
dash uses /etc/profile, ~/.profile, and $ENV (if available). grep your
username from /etc/passwd to find your shell.
On Thu, Feb 27, 2014 at 12:04 PM, sean wrote:
> No, we want the output of :
>
> which killsol.sh
>
> "which" tells you where "killsol.sh" is in your path.
>
> And by "doesn't wo
No, we want the output of :
which killsol.sh
"which" tells you where "killsol.sh" is in your path.
And by "doesn't work" I mean when it is apparently not found in your
path. I want to see what "which" says when your shell does not run
"killsol.sh" by itself.
On Thu, Feb 27, 2014 at 11:59 AM, Da
Sean, there is no output from killsol.sh. It either kills the desired
process or does nothing. And it DOES work when it actually gets run.
Nathan, .profile actually checks to see if the is a .bashrc and if so, runs
it so putting in what you suggest would create an infinite loop. BUT, you
gave m
I know different shells source different files when started, I'm curious
to know which shell you are using.
(konsole, gnome-terminal, ...)
If it works after sourcing your .profile then I would bet you need to
have a .bashrc file with a line that says source ~/.profile.
Like Kitepilot, I too
What's the actual output of `which killsol.sh` when it's not working?
It should say "which: no killsol.sh in ($PATH)". This will probably
not have /home/larry/bin.
man bash, see: INVOCATION to figure out where (and which) files need
to be. Upstream bash does not include ~/bin in the path by defaul
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 come
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 executab
16 matches
Mail list logo
