12

I have a couple of commands that I need to run. These commands needs to continually run even after I exit my interface. When I have access to the Linux GUI, I execute something like:

cd /home/testuser/Scripts*
xterm -hold -T "Background_Script1" -e  "service1-start.sh" &
sleep 10
xterm -hold -T "Background_Script2" -e "service2-start.sh" &

Any help will be much appreciated.

Shadok
  • 4,070
user3331952
  • 123

5 Answers5

32

Try

nohup Background_ScriptX &

nohup ensures that a process is not terminated when a terminal is closed. The & symbol pushes the process into the background.

Hope this was helpful.

Eamonn Travers
  • 526
19

If you want to read the output at a later date, you can use screen:

screen -d -m my_command

This gives you a detached terminal you can connect to later (screen -r) to read the stdout/stderr output.

Mark
  • 1,608
5

Another option if nohup command is not available is to use the disown command.

First you can view your background tasks by running jobs in terminal. You can get the job number from there.

Now just run disown %[job number] and the process will be detached from the current terminal and stay alive when you log out.

Side note: Make sure that you are asking the correct question. If you are running actual services as you hint in your sample you might want to look into how to create a daemon in the OS of your choice. This is to make sure that the process still runs after a reboot and make it more consistent with other services.

Hope this helps.

jus1in
  • 5
user391035
  • 386
3

Since screen has been mentioned: there are other terminal multiplexers out there. I like tmux very much, see e.g. this other superuser question, tmux vs screen for a comparison.

Community
  • 1
1k5
  • 131
0

You can also try: setsid Setsid also works to background programs and allows them to keep running after the terminal/ssh session is disconnected.

Use it like this:

setsid program-to-background

Manpage: http://man7.org/linux/man-pages/man2/setsid.2.html

nulldev
  • 15