Differences

This shows you the differences between two versions of the page.

--- getting_started:deploy:deploy_host [2026/04/10 17:20] – [Allow Realtime Priorities] ursgraf
+++ getting_started:deploy:deploy_host [2026/04/12 16:57] (current) – [Working on the Host] ursgraf
@@ Line 9: / Line 9: @@
 $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/you/work/eeros-project/install-x86/lib/
 </code>
-Please keep in mind that this path setting is valid for the current shell. As soon as you start a new shell, you have to repeat the step. \\
+Please keep in mind that this path setting is valid for the current shell. As soon as you start a new shell, you have to repeat the step.
-There is one more difficulty. If you start your application with ''sudo'', as you often have to do, you must prepend the call with
+There is one more difficulty. If you start your application with ''sudo'', you must prepend the call with
 <code>
 $ sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} ./yourExample
@@ Line 18: / Line 19: @@
 $ sudo LD_LIBRARY_PATH=/home/you/work/eeros-project/install-x86/lib/ ./yourExample
 </code>
+Keep in mind that it is preferable to not run your EEROS application with ''sudo''. This can lead to problems when working together with ROS. ''sudo'' is necessary when the executor tries to alter scheduling parameters or when certain device file such as ''/dev/mouse'' or ''/dev/ttyUSB0'' must be accessed. Follow directions given in [[getting_started:tutorials:rttest|]] or [[getting_started:tutorials:inputdev1|]] to avoid running your program with ''sudo''.
+Keep in mind that if you have built EEROS with ROS support, you have to source the setup script before running any EEROS application as given in [[getting_started:ros_prep|]].
-===== Allow Realtime Priorities =====
-All examples using the executor will have to change thread priorities to make them realtime capable. You could run these examples with ''sudo'', but it is preferable to give your current user the privilege to change scheduling parameters. Running with ''sudo'' can cause issues when using ROS2 and is not recommended due to security reasons. Edit the file ///etc/security/limits.conf// (on Ubuntu) and add the following lines:
-<code>
-your_username   soft    rtprio  99
-your_username   hard    rtprio  99
-your_username   soft    memlock unlimited
-your_username   hard    memlock unlimited
-</code>
-Log out and log back in in order for the changes to take effect.
 ===== Examples =====
-If you have followed the instructions given in [[getting_started:install:use_on_host|]], [[getting_started:compile_eeros_host|]] and [[getting_started:write_app:use_on_host|]] you can call the examples as follows:
+===Running your Example Application===
+If you have followed the instructions given in [[getting_started:install:use_on_host|]], [[getting_started:compile_eeros_host|]] and [[getting_started:write_app:use_on_host|]] you can call your EEROS application as follows:
 <code>
@@ Line 38: / Line 35: @@
 No root privileges and no other libraries are necessary.
+===Running the Built-in Examples===
 If you want to run the built-in examples of EEROS
 <code>
 $ cd ~/eeros-project/eeros/build-x86
-$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/you/work/eeros-project/install-x86/lib/
 $ ./examples/logger/loggerTest
 </code>
-No root privileges are necessary but you have to set your library path.
-<code>
-$ sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} ./examples/rtTest/rtTest
-</code>
-You need root privileges and have to pass your library path.
-<code>
-$ cd ~/eeros-project/build-x86/eeros
-$ sudo LD_LIBRARY_PATH=${LD_LIBRARY_PATH} ./examples/system/systemTest1 -c examples/system/SystemTest1Config.json
-</code>
-You need root privileges and the eeros and simulator libraries must be found. Further, you have to specify a hardware configuration file.
 Continue with having a closer look at the examples in EEROS as described in [[getting_started:tutorials:start|]].