Linux commands useful when performing heavy processing

ko31 profile image Ko Takagi ・1 min read


The sleep command suspends processing for a certain period of time.

For example, when running a heavy shell script, using the sleep command moderately can reduce the load.

# Delay 10 seconds(no option)
sleep 10

# Delay 10 seconds
sleep 10s

# Delay 5 minutes
sleep 5m

# Delay 3 hours
sleep 3h
Enter fullscreen mode Exit fullscreen mode


The nice command can be executed with priorities.

For example, when performing a backup or batch process, the process can be performed without affecting other processes.

You will be able to batch process more safely, even at lunchtime when the website is crowded by many people.

# Without option, run at +10 priority
nice /path/to/command

# Run at +10 priority
nice -n 10 /path/to/command
Enter fullscreen mode Exit fullscreen mode

Priority options can be specified from -20 (higher) to 19 (lower). However, negative values can only be specified by superuser.

You can also use the renice command to adjust the priority of already running processes.

# Adjust the priority of pid 99999 process
renice 10 -p 99999
Enter fullscreen mode Exit fullscreen mode


If you use the nohup command, you can continue processing even if you log out of the terminal.

After executing the command, you can close the computer and go to bed calmly.

nohup /path/to/command &
Enter fullscreen mode Exit fullscreen mode

Standard output during execution of the nohup command is saved in the nohup.out file.

Posted on by:

ko31 profile

Ko Takagi


I am freelance web engineer in Japan. Since I am studying English, I started writing articles here😆 I want to play catch! ⚾️


Editor guide

and nohup does NOT work, like ... NEVAH, EVAH, maybe it was working when security wasn't in such TOTAL PARANOIA, BY DEFAULT, but those ages ended decades ago ... "nice" articol


I'm sorry. I'm not sure what you mean because I'm not good at English...


I think your ability at understanding English isn't the problem here so much as the ability of ttrash to write it.

nohup works fine on most modern systems as far as I can tell, as you mentioned in your sample of using it you can't just run nohup <some command> and get on with your day.

I suspect ttrash was referring to this sort of language in the info pages:

'nohup' does not automatically put the command it runs in the background; you must do that explicitly, by ending the command line with an '&'. Also, 'nohup' does not alter the niceness of COMMAND; use 'nice' for that, e.g., 'nohup nice COMMAND'.

ie. You need to disconnect your terminal from the command explicitly and you can't use any shell-built-ins in your command because it won't understand them. Nothing stopping you writing a script with an appropriate shebang and executing that with nohup, appended with an & to detach your terminal of course.

Also plausible that ttrash had fallen victim to job control in a shell, in something like zsh you would want to use a &! to disown the background running job so that your shell session could be gracefully closed.

Yup, nohup will do exactly what it says, it's never failed me though I suspect understanding what it does may be causing this issue as its not obvious.

There is a signal in Unix systems called SIGHUP. When a terminal is controlling a process (ie that process was started in that terminal) and that terminal is closed it will send SIGHUP to those processes. Most processes by default treat SIGHUP like SIGTERM but some do different things with it. If you expect it always to do SIGTERM, i.e. terminate the process then it won't always. All nohup does is catch the SIGHUP the terminal sends it (or is manually sent) and blocks it going to the process. It won't block something sending SIGHUP directly to the child process nor will it guarantee what the child process will do if it receives SIGHUP.

Some processes choose to do other things with SIGHUP like restart the process running. If you send SIGTERM to nohup it will send that on to its child process too and terminate that, so if you don't put the process in the background and ctrl-c then the child process will terminate too. If you forget to put the process in the background with an ampersand the best way is to do ctrl-z to stop it and then bg puts it in the background. Beyond the terminal hanging up nohup will basically do nothing.

Hope that clears it up a bit, I didn't understand this for a time I know.

Personally I'm not a huge fan of using nohup for things because it either essentially just makes your terminal hang or you need to disconnect from the job, but Reconnection is somewhat pointless.

I've found that using disown -h (not defined in posix so YMMV, and Actually I'm pretty sure this is a bashism) to disown jobs that I want to run in the background but not remove from the job table (ie. I can more easily reattach to them later if I want but the HUP sent by terminal closure doesn't impact them).

Or,and even better solution, install something like screen or tmux, eventually if you get into the habit of always launching a screen or tmux session when you log in then you can always reattach to your previous session, assuming the job hasn't finished and $TMOUT isn't set.


'nohup' is nice, but needs to be fired proactively. I prefer 'disown' which can be executed after launch.


That's good! I didn't know disown, so I'll look into how to use it.


You can also use renice to adjust the priority of a process once it's already running.


Thanks! I added renice to this article.