LINUX nohup command input and output shades in and out

The output is appended to the Nohup.out file in the current directory, regardless of whether the output of the Nohup command is redirected to the terminal. If the nohup.out file for the current directory is not writable, the output is redirected to the $HOME/nohup.out file.

AD:WOT2015 Internet operations and developers Conference selling tickets

You may encounter the Nohup command problem, here will explain the nohup command problem resolution, Linux itself is the core part of the operating system, that is, the operating system kernel. The kernel is the most basic operation of the program, it is responsible for other programs (such as the text editor program) Start and end, memory request processing hard disk access, network connection management and other aspects of work. Unix/linux generally want to let a program run in the background, many use & at the end of the program to let the program run automatically.

For example we want to run MySQL in the background:/usr/local/mysql/bin/mysqld_safe–user=mysql & But many of our programs do not have the same daemon as mysqld, and maybe our program is just a normal program. In general, if the terminal is closed, the program will be closed even if the & end is used. In order to be able to run in the background, we need to use the Nohup command, such as we have a start.sh need to run in the background, and want to be able to run in the background, then use Nohup:

Nohup/root/start.sh &

Prompt after carriage return in shell:
[The standard output of the ~]$ appending output to Nohup.out is automatically redirected to the Nohup.out file in the current directory, which plays the role of log. But sometimes in this step there is a problem, when the terminal is closed, the process will be automatically closed, see Nohup.out can be seen in the shutdown Terminal Instant service automatically shut down. After consulting the Red Flag Linux engineer, he also can not be solved, after executing on my terminal, the process that he starts is still running after shutting down the terminal.

The second time I showed it, I found out that I was in a different detail than when he operated the terminal: he was prompted by the Shell to return to the Shell Input Command window by pressing the keyboard key on the terminal, and then exit the terminal by entering exit in the shell Nohup , and I'm the one that closes the terminal after the Nohup executes successfully after the Close Program button. So this time will be broken the corresponding session of the command, resulting in nohup corresponding process is notified need to shutdown together. This detail has not been noticed by me, so I recorded it here.

Attached: nohup Command Reference nohup command
Purpose: To run the command without hanging off.
Syntax: Nohup Command [Arg ...] [&]
Description: The nohup command runs commands specified by the command parameter and any related ARG parameters, ignoring all hang-up (SIGHUP) signals. Use the Nohup command to run a program in the background after logging off. To run the Nohup command in the background, add & (the symbol representing "and") to the end of the command.

The output is appended to the Nohup.out file in the current directory, regardless of whether the output of the Nohup command is redirected to the terminal. If the nohup.out file for the current directory is not writable, the output is redirected to the $HOME/nohup.out file. If no file can be created or opened for appending, then the command specified by the commands parameter is not callable. If the standard error is a terminal, then all output of the specified command to the standard error is redirected to the same file descriptor as the standard output.

Exit Status: This command returns the following exit values: 126 You can find but cannot invoke the command specified by the command parameter. The 127 nohup command has an error or cannot find the command specified by the commands parameter. Otherwise, the exit status of the Nohup command is the command parameter that specifies the exit state of the nohup.

Nohup command and its output file

Nohup command: If you are running a process and you feel that the process will not end when you exit the account, you can use the Nohup command. This command can continue to run the process after you exit the account/close the terminal. Nohup is the meaning of not hanging (n ohang up).

The general form of this command is: Nohup Command & Submit job with nohup command
If you submit a job using the Nohup command, all output from the job is redirected to a file named Nohup.out by default, unless the output file is specified separately:
Nohup command > Myout.file 2>&1 & In the example above, the output is redirected to the Myout.file file. Use jobs to view tasks. Use FG%n to close.

There are also two commonly used FTP tools Ncftpget and Ncftpput, can be implemented in the background FTP upload and download, so you can use these commands in the background to upload and download files.

LINUX nohup command input and output shades in and out