Subject: From: Date:

Re: [ecs] Linux auto-cmds at login Ingo Pakleppa 27 Oct 2003 23:45:43 -0800

---

On Mon, 2003-10-27 at 17:13, Mark Gilmore wrote:
> The goal for this KNOPPIX application:
> I need to run ECS when knoppix logs in the "knoppix" user
> (which it does *automatically* at bootup).
> The ECS cfg will then run a JAVA pgm after init.
> There is *no* browser access.
> btw, I don't know if I need to start a bash session to run a JAVA pgm.
> 
> In trying to empirically determine where to place the commands
> (a perpetual problem), I created the following files with contents following:
>          /home/mark/.bashrc
>                  echo x > bashrc.tmp
>                  edm.bin
>          /home/mark/.bash_profile
>                  echo x > bash_profile.tmp
>                  edm.bin
>          /home/mark/.profile
>                  echo x > profile.tmp
>                  edm.bin
> When I logged in, only bashrc and bash_profile were executed
> (as their .tmp files were created).
> edm.bin was *not* run by any (but perhaps I need to start a bash session 
> 1st ??).
> I also note that my command prompt was changed to "bash-2.05b$" (??).

This is the default bash prompt. Which tells me that you are either
indeed running a new instance of bash, or in the process clobbered (or
failed to call) the file that set the prompt. On my system, /etc/bashrc
is responsible for setting the prompt (related to the $PS1 environment
variable). This file gets called from .bashrc, so if you replaced
.bashrc and did not include calling /etc/bashrc, that would explain why
the prompt changed.

And you are right, there is no such thing as a .profile.

As for your main question, the first things to check are:

- is edm.bin in the path? Since your $PS1 environment variable didn't
get set, I suspect that your path variable also didn't get set. Easy way
to test this: instead of running edm.bin, try specifying the fully
qualified path.

- are the permissions for edm.bin correct?

---