Ask Your Question

brendan's profile - activity

2017-10-13 20:51:21 -0500 received badge  Good Question (source)
2016-01-26 19:42:05 -0500 received badge  Nice Question (source)
2015-06-19 13:55:26 -0500 received badge  Popular Question (source)
2015-06-19 13:55:26 -0500 received badge  Notable Question (source)
2015-06-19 13:55:26 -0500 received badge  Famous Question (source)
2015-03-25 22:21:06 -0500 received badge  Student (source)
2015-03-25 18:21:40 -0500 asked a question How to reference environmental variables inside an upstart installed launch file?

I have successfully managed to install a launch file but upon rebooting found that none of the environmental variables referenced in the launch file are found. Granted, the launch files are guilty of liberal usage of $(optenv VARIABLE default) and as such many things are taking the default value. This now makes sense because, as I understand it, services run with most of the environmental variables stripped away. However I'd really like to avoid simply hard code the information into the launch files because the robot's hardware configuration is saved in these variables and this one launch file has to be installed on several different types of units.

I saw that for normal linux services the work around is to source an additional file inside the service file but I even find where robot_upstart installs the newly created service, which I confusingly called ros as well. I didn't see it /etc/default or /etc/init.d . My best guess was to source the ".robotrc" in the devel/setup.bash and include it with --setup option?

Thanks