[SOLVED] Issue: Bash script displays its name upon execution

gacanepa · 07-08-2013, 10:03 AM

Hi everyone,
I just noticed a rather annoying issue. Whenever I run a bash script, the first thing that it does is display the name of the script along with all the arguments passed to it (if there are any). However, nowhere in the script there is anything that provokes that behavior.
See for example:

Code:

gacanepa@debian:~/scripts/bash/tests$ ./if_regex.sh 345-14-45
./if_regex.sh 345-14-45
You provided the following argument: 345-14-45
yes

where if_regex.sh is:

Code:

#!/bin/bash
echo "You provided the following argument: $1"
glob="[[:digit:]][[:digit:]][[:digit:]]-[[:digit:]][[:digit:]]-[[:digit:]][[:digit:]]"
if [[ ${1} == $glob ]]; then
    echo "yes"
else
    echo "no"
fi

The same issue happens with other scripts as well

. Any ideas as to why this is happening?

jdkaye · 07-08-2013, 10:53 AM

I can't replicate your results. I created an if_regex.sh executable file and stuck it in /tmp. I then ran it and here is the outcome:

Code:

tmp$ ./if_regex.sh 345-14-45
You provided the following argument: 345-14-45
yes

The script is copied from yours and pasted into the if_regex.sh that I created in /tmp
There are only two differences:
1. I created the script in /tmp %I can't see that that should matter.
2. I made it executable

Code:

chmod ugoa+x if_regex.sh

Other than that I did everything exactly as you did. Maybe we have a difference in our bash profile file?
A true mystery.
jdk

gacanepa · 07-08-2013, 11:00 AM

Quote:

Originally Posted by jdkaye

I can't replicate your results. I created an if_regex.sh executable file and stuck it in /tmp. I then ran it and here is the outcome:

Code:

tmp$ ./if_regex.sh 345-14-45
You provided the following argument: 345-14-45
yes

The script is copied from yours and pasted into the if_regex.sh that I created in /tmp
There are only two differences:
1. I created the script in /tmp %I can't see that that should matter.
2. I made it executable

Code:

chmod ugoa+x if_regex.sh

Other than that I did everything exactly as you did. Maybe we have a difference in our bash profile file?
A true mystery.
jdk

I actually thought about the bash profile file but the only modification I made to it was setting vim as my default editor. And that was more than a week ago, whereas I just noticed this "issue" earlier this morning (and I've been scripting all along).

Doc CPU · 07-08-2013, 11:16 AM

Hi there,

Quote:

Originally Posted by gacanepa

I actually thought about the bash profile file but the only modification I made to it was setting vim as my default editor. And that was more than a week ago, whereas I just noticed this "issue" earlier this morning (and I've been scripting all along).

in Windows (and formerly in DOS) there was an option for the console that would echo every command line after expanding variables, and before executing it. It looks very much like this is what's happening here. Is there a global setting like that for bash? I haven't heard of one yet, but that means nothing ...

[X] Doc CPU

gacanepa · 07-08-2013, 11:20 AM

Another thing I just noticed. It seems that this is happening not only for scripts but for all commands as well. I just typed

Code:

man bash

and before actually displaying the man page for bash, it showed "man bash" in a separate line and then displayed the man page.
Really weird.

gacanepa · 07-08-2013, 11:29 AM

You may not believe this, but I just restarted the server and the issue seems to be gone

. Who know what was the cause.
Anyway, I will mark the previous answers as helpful so that it adds to the reputation of everyone who tried to help. I really appreciate it.

Z038 · 07-08-2013, 11:33 AM

What you are describing sounds like you have the bash -v option set.

Check ~/.bashrc, ~/.bash_profile, ~/.bash_login, ~/.profile, /etc/profile, /etc/bash.bashrc and see if you are executing a "set -v" command, or "set -o verbose".

Also, if you issued set -v in a login shell or command window, it would have the same effect.

gacanepa · 07-08-2013, 11:35 AM

Quote:

Originally Posted by Z038

What you are describing sounds like you have the bash -v option set.

Check ~/.bashrc, ~/.bash_profile, ~/.bash_login, ~/.profile, /etc/profile, /etc/bash.bashrc and see if you are executing a "set -v" command, or "set -o verbose".

Also, if you issued set -v in a login shell or command window, it would have the same effect.

Thanks!

jdkaye · 07-08-2013, 02:17 PM

Quote:

Originally Posted by gacanepa

Anyway, I will mark the previous answers as helpful so that it adds to the reputation of everyone who tried to help. I really appreciate it.

I don't do reputations (mine is irreparably damaged anyway) but if my post was helpful that's reward enough. There is a new moon tonight so that is obviously the reason for this mysterious behaviour.
jdk