Currently, Conler does not provider user with a handy way to select launch-mode – all applications are launched sequentially.
- But the following workaround is possible:
Create a shell script like that one:
#!/bin/sh $@ &Name it, for example, /usr/local/bin/run-in-background.sh and make it executable
Modify your command in Command List to look like:
/usr/local/bin/run-in-background.sh /my/program -arg1 -arg2:value
Currently, Conler does not provide user with a handy way to collect program’s output.
- But the following workaround is possible:
Create a shell script like that one:
#!/bin/sh $@ 2>&1 > /tmp/launch.logName it, for example, /usr/local/bin/run-logged.sh and make it executable
Modify your command in Command List to look like:
/usr/local/bin/run-logged.sh /my/program -arg1 -arg2:valueOutput of launched application will be stored in /tmp/launch.log
Note
This functionality is planned to be implemented in the further versions
- Most common mistakes:
- You are trying to run a GUI application which can’t find set $DISPLAY variable
- You are trying to run an application which can’t be run with root privileges
- You are trying to run an application using relative path such as ../../my-program.sh or just my-program.sh. Use always absolute path instead.
- You are trying to run an application which requires interaction with the user.
Currently Conler doesn’t set up environment variables by itself when run application with non-root privileges. It uses special run wrapper written on shell /usr/bin/conler-run-wrapper.sh.
- You can (OR):
Modify run wrapper to use custom environment variables
Make your own copy of run-wrapper and use it in way:
- Run command in SUPERUSER environment
- Command should look like: /usr/bin/my-custom-run-wrapper.sh /my/program.bin -arg val