A common way of running bash commands in background is attaching “&” to the end of the command. But what happens if you need to run a sudo command in the background? Appending “&” to the end of “sudo whatever.sh &” will not work. According to this thread on SlackOverflow:
The problem is that the
sudocommand itself is being run in the background. As a result, it will be stopped (SIGSTOP) when it tries to access the standard input to read the password.
A simple solution is to create a shell script to run
synaptic &and then
sudothe script in the foreground (i.e. without
Yes, making a wrapper script that runs a sudo command and then calling this wrapper script with “&” at the end is a common way, but there is another alternative that I like (especially when you don’t really care about command output): use screen utility:
screen -d -m sudo whatever.sh
This will create a new detached screen session and run a sudo command inside of it without blocking the terminal (or program execution, if you run the command from some other script/program). If the command is long running, you will be able to attach screen and see output. When command completes execution, the screen session will be terminated.
Will leave it here for future reference.