Hello,
I find quite useful to start my launch inside a screen to be able to
monitor it easily after boot time if needed.
Otherwise, I use the same setup
HTH
On 10/25/2010 09:27 PM, Blaise Gassend wrote:
> I do the following:
>
> 1. I have an init.d script that sources the correct setup.sh, and
> rosruns the actual init.d script in a ROS package.
> 2. The init.d script in the ROS package uses start-stop-daemon, or
> your distro's variant to start/stop roslaunch.
>
> I do this two step method because I always find myself wanting to make
> simultaneous changes to the launch file and the init.d script. By
> having only a stub in /etc/init.d, I can pretty much guarantee that
> the stub never has to change.
>
> On Mon, Oct 25, 2010 at 10:34 AM, Robbie Plankenhorn
> <rplankenhorn@gmail.com> wrote:
>
>> I have been trying to get my ROS stack to launch automatically when Ubuntu
>> starts up and I am having some issues. I have tried to implement an init
>> script but I wasn't able to get it to work. I think it has something to do
>> with the setup.sh init scripts that are required to be in the .bashrc file
>> in order to find the stack.
>> What is the best way to get an ROS stack to start at boot time? Is this the
>> correct approach? If so, then are their any tricks to getting it to work?
>> Thanks,
>> Robbie
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>>
>>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
--
Cedric - Specialising in cat herding
-
http://www.asl.ethz.ch/people/cedricp
-
http://www.skybotix.com
(text/plain)