Sorry if this is in the wrong place, I'm new.
I have a resource manager (RM, a program which opens up and sits on other processes) that I am attempting to run on startup. I can run the program successfully, however the processes which start under it will not run at all. I've placed a script in /etc/init.d that calls another script which starts up the RM. If I do not start the RM on boot-up, but rather just run the script which starts it after I've logged in, it runs fine.
I initially thought that it the environment variables weren't getting set right (since the processes depend on these enviroment variables for execution), but I echo'ed the env to a file and all the pertinent variables are there. Any help would be most appreciated.
I su to myself so that I'm not running it as root.
I have Redhat 7.2-something, I can't find the exact version number.
Hopefully I've given you all the pertinent information. Thanks in advance.
If your script depends on bash environment variables to be set before it works correctly, you will not be able to run it at boot. Bash environment variables are set when a user logs in.
When a user logs in bash reads and executes commands, if the files exist, in this order:
/etc/profile, ~/.bash_profile, ~/.bash_login, ~./profile
Jim H
I need some help clearing this up. If my script, or rather the program run by the script, depends on environment variable THIS_ONE, and I 'echo' the 'env' to a file and THIS_ONE shows up and has the correct value, shouldn't the program have the environment variable it needs? Whew, what a sentence.
It seems to me that if the environment is setup correctly before the program is executed, it should have the variables it needs. So, if I check the 'env' just before executing the program, it should relay the 'env' at that point.
I'm using 'su [my_user_name] -c [command]' which I was given to understand, started a new shell of the type the user uses. This seems to be confirmed in the 'env' which indicates a tcsh.
Sorry if I seem a bit dense, I'm just trying to get a handle on this. Thanks.
Yes, but only if the env variable exists. If your program relies on an env variable that does not exist until the user logins then the program won't work at boot.Originally Posted by Schion65
Jim H
Ok, so if the env variable does not exist then my program will not work, I'm clear on that. What's a little fuzzier is how I check for existance. I was assuming, perhaps incorrectly, that if the variable shows up in the env just before the program is executed (i.e. inside the script that executes the program, which I'm told is it's own shell) then the variable exists.
Have I misunderstood? If so, how can I ensure that all of my env variables are in existance before I execute the program? Thank you.
Schion
Insert some temporary debugging lines in your script.
Maybe when the script executes have it create a log file, then as it looks for each env variable have it output to the log file whether or not the variable exists and its value. If everything is good there then we will know the problem is elsewhere.
Jim H
I have the script output to a log file the env variable that the program depends on. It shows up and its the correct name. So, I'm still unsure as to why it's not executing correctly. Thanks again.
The type of program are you starting with the script? C/C++? Perl, python, etc.....?
I will probably need to see the script now.
Where exactly did you install your script? Did you place a symlink to it in the right directory for the runlevel you are booting?
Jim H
I am starting a C++ program, which starts other C++ programs.
I'll put the scripts below. I installed my script in init.d, and I placed a S98Name link in rc3.d (I'm using run level 3), and a K98Name link in rc6.d.
As for the scripts, the first script is the one in init.d, that calls the second script. The second script calls scripts which start the individual programs. The reason I did this is because I want to have scripts which will monitor these programs and retart them should they die (note:I've not put this functionality in yet). Sorry if this is a little confusing, I'm constrained by my requirements.
The startMW and startSsmbg both function perfectly. Lrm itself appears to work, however, any processes started by it do not work.
------------------
#!/bin/sh
# Startup script for RSS
#
# Source function library.
. /etc/rc.d/init.d/functions
insmod /home/swalton/dev/PHOTONICS/src/pmw/common/viper/rgb/viper_rgb.o
insmod /home/swalton/dev/PHOTONICS/src/pmw/common/viper/quad/viper_quad.o
var=$(env)
echo "$var" >& /tmp/RSSenv
prog="RSS"
start() {
echo -n $"Starting $prog: "
su sbrennan -c /home/sbrennan/build/bin/startRSS
RETVAL=$?
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/anacron
echo
return $RETVAL
}
stop() {
echo -n $"Stopping $prog: "
killproc /home/sbrennan/build/bin/startRSS
echo
RETVAL=$?
return $RETVAL
}
case "$1" in
start)
start
;;
stop)
stop
;;
status)
status /home/sbrennan/build/bin/startRSS
;;
restart)
stop
start
;;
*)
echo $"Usage: $0 {start|stop|restart|status}"
exit 1
esac
exit 0
--------------startRSS
#!/bin/bash
#
# Script to start a screr, the Lrm, and Ssmbg.
# Note: Certain env's must be set prior to execution.
#
cd /home/sbrennan/build/bin
var=$(env)
echo "$var" >& /home/sbrennan/startRSSenv
./startMW
./startSsmbg
./startLrm
---------------------startLrm
#!/bin/bash
#
# Script to Start the LRM ( Should be run in Host Machine )
#
IP_ADDRESS=###.#.#.#
NETWORK_PORT=16000
LOCAL_PORT=16001
LRM_GTI=1000
BINDIR=/home/sbrennan/build/bin
var=$(env)
echo "$var" >& /home/sbrennan/startLrmenv
echo "$APP_CONFIG_DIR" >& /home/sbrennan/APPpresent
${BINDIR}/RSSlrm.linux ${IP_ADDRESS} ${NETWORK_PORT} ${LOCAL_PORT} -1 0 0 18888
MW_LRM r 0 0 0 f &
Posting Permissions
Reply With Quote
Bookmarks