Use of screen and glitch

Small topic:

If the terminal is actually broken when we compile the software, according to theory, the program under this terminal will end. Compiled the long time, white busy. Then you can use the screen program.

Screen simulates more than one virtual window, and when the screens analog terminal is disconnected, screen's terminal does not exit and the program continues.
Screen opens a new screens virtual interface
can also hide the open screen terminal, return to the original terminal, of course, the original terminal is not disconnected in the case.

CTRL + A, press Ctrl+d again. or direct ctrl+a,d. Click A, and then click D.

To return to screen terminal, check the id:screen-ls of each screen terminal first
Open screen Terminal: Screen-r screen_id
Only one screen terminal case, directly with the Screen-r can be opened.

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/78/BD/wKioL1aCb-qRque_AABvzV3PbsU471.jpg "style=" float: none; "title=" 043.jpg "alt=" Wkiol1acb-qrque_aabvzv3pbsu471.jpg "/>

After the Ctrl+a,d or screen terminal is broken, the screen process's parent process becomes init. Out of the parent-child relationship with this terminal. So the program in screen will not be interrupted after the end of the terminal.

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M00/78/BD/wKioL1aCb-WBHpPQAADMquh_zRQ914.jpg "style=" float: none; "title=" 041.jpg "alt=" Wkiol1acb-wbhppqaadmquh_zrq914.jpg "/>

When the Screen-r ID is opened with a new terminal connection, screen communicates with the parent process, the screen of init (guessing by itself).

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/78/BF/wKiom1aCb8eRoz22AADWQHZrC48378.jpg "style=" float: none; "title=" 040.jpg "alt=" Wkiom1acb8eroz22aadwqhzrc48378.jpg "/>

a glitch: When the analog terminal is disconnected, and then re-connected to see screen is still running, but the previous SSH terminal has not been disconnected, so screen is the previous sshd sub-process. This situation cannot be reconnected to screen.

You can manually close the previous sshd process and then reconnect the screen. ：

View the Scrren information and connect to the screen that was prompted to screen attached process.

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M02/79/0E/wKiom1aGShmxO_5zAABhWcWWhuE192.jpg "title=" 090. JPG "alt=" wkiom1agshmxo_5zaabhwcwwhue192.jpg "/>

Let's take a look at the current process tree.

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M00/79/0E/wKiom1aGSnvxAZ26AADq4HQDaCc546.jpg "title=" 091. JPG "alt=" wkiom1agsnvxaz26aadq4hqdacc546.jpg "/>

The terminal is disconnected, but the sshd process of the terminal is not disconnected, and screen above does not transfer the parent process.

Check the process ID of the sshd and half-closed.

Pstree-p View the process tree and display the ID.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/79/0E/wKiom1aGSyfy7dIhAACCgn34t6U984.jpg "title=" 092. JPG "alt=" wkiom1agsyfy7dihaaccgn34t6u984.jpg "/>

Close it.

650) this.width=650; "src=" http://s4.51cto.com/wyfs02/M01/79/0C/wKioL1aGS7zz_dCDAADzd7AnEfU458.jpg "title=" 093. JPG "alt=" wkiol1ags7zz_dcdaadzd7anefu458.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/79/0E/wKiom1aGTCWSYfqmAAAyaA4sTXc623.jpg "title=" 094. JPG "alt=" wkiom1agtcwsyfqmaaayaa4stxc623.jpg "/>

You can see that it is normal.

This article is from the "Big Tomato" blog, be sure to keep this source http://fanqie.blog.51cto.com/9382669/1730685

Use of screen and glitch