Well, as I understand, whenever we start a terminal the .bashrc is executed and it can be like this:

# .bashrc

# User specific aliases and functions

# Source global definitions

if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi

And the bashrc executes the *.sh files in /etc/profile.d.

I have done a configure.sh that I want to be executed for all the users when they open a terminal, but if comes out that it is only executed for the root.

Does someone know why?, and if it isn't the way,
how can I do to make work the configure.sh for all the users when they log in?

thnx.
Aizkorri.

Maybe you have different .bashrc files for different users? And make sure all users can execute /etc/bashrc .

.bashrc resides in peoples home directories correct??

Right.

Could you maybe post the Configure.sh script so we could look at it? Maybe you are making calls to programs or scripts outside of the users path (such as programs in /sbin or /usr/sbin).

Thanks for the answers, yes, the users could not execute the bashrc, but I'm not sure if it is good to give them this right.
This is the configure.sh

PATH="$PATH:/usr/bin/"
INFO=/usr/lib/INFO
export DATA PATH

I want them to be able to execute an application
'/usr/bin/usrprofile' that uses the data that is in INFO.
any suggestion?

If you don't want it *executed* but only *available* to ppl IMO add it to /etc/profile (which is mode 0644, not 755, btw):
if ! echo $PATH | /bin/grep -q "/usr/lib/info" ; then
PATH="$PATH:/usr/lib/info"
fi
# Only export DATA_PATH if your app *needs* the variable in the env
# DATA_PATH=/usr/lib/info
# then add it to the export line:
# export <the other declarations> DATA_PATH