Table of contents
Combined revision comparison
...
As shown below, the vpnserver process is launched in two stages on the UNIX version VPN Server. First, the first process named execsvc is launched as a background process, after which that process creates a child process using the fork() system call, and this child process carries out the actual VPN processing. The parent process (process ID 1549 in the example below) constantly monitors the child process (process ID 1550 in the example below) and in the event that an abnormal error occurs, immediately terminates the process and launches it again to attempt recovery (see 3.3 VPN Server Administration for details). The example below was actually runsrun on a particular Linux system so it may not appear the same on different Linux or other operating systems. In addition, in order to display multiple threads as multiple processes in the case of versions with old Linux kernels (i.e. versions not compatible with native threads), the actual vpnserver processes created may be more than those in the example below but this is a display issue and operation is in fact normal.
...
Although thisit only occurs rarely, in the event that the VPN Server process launched in User Mode goes out of control for some reason such as a hardware malfunction (a memory shortage, for instance) and is unable to be stopped by vpnserver /stop, first forcibly terminate the parent vpnserver process (process ID 1549 in the example above) by sending a signal to it using kill -KILL, then forcibly terminate the remaining process (process ID 1550 in the above example) by sending a signal to it with kill -KILL. Forcibly terminating the child process first may cause the parent process to determine that the child process terminated abnormally and launch it again. Depending on the system, killall -KILL vpnserver may enable the simultaneous termination of all vpnserver processes.
...
Version from 16:31, 4 Mar 2013
...
As shown below, the vpnserver process is launched in two stages on the UNIX version VPN Server. First, the first process named execsvc is launched as a background process, after which that process creates a child process using the fork() system call, and this child process carries out the actual VPN processing. The parent process (process ID 1549 in the example below) constantly monitors the child process (process ID 1550 in the example below) and in the event that an abnormal error occurs, immediately terminates the process and launches it again to attempt recovery (see 3.3 VPN Server Administration for details). The example below was actually run on a particular Linux system so it may not appear the same on different Linux or other operating systems. In addition, in order to display multiple threads as multiple processes in the case of versions with old Linux kernels (i.e. versions not compatible with native threads), the actual vpnserver processes created may be more than those in the example below but this is a display issue and operation is in fact normal.
...
Although it only occurs rarely, in the event that the VPN Server process launched in User Mode goes out of control for some reason such as a hardware malfunction (a memory shortage, for instance) and is unable to be stopped by vpnserver /stop, first forcibly terminate the parent vpnserver process (process ID 1549 in the example above) by sending a signal to it using kill -KILL, then forcibly terminate the remaining process (process ID 1550 in the above example) by sending a signal to it with kill -KILL. Forcibly terminating the child process first may cause the parent process to determine that the child process terminated abnormally and launch it again. Depending on the system, killall -KILL vpnserver may enable the simultaneous termination of all vpnserver processes.
...
Version as of 12:05, 26 Mar 2014
...
As shown below, the vpnserver process is launched in two stages on the UNIX version VPN Server. First, the first process named execsvc is launched as a background process, after which that process creates a child process using the fork() system call, and this child process carries out the actual VPN processing. The parent process (process ID 1549 in the example below) constantly monitors the child process (process ID 1550 in the example below) and in the event that an abnormal error occurs, immediately terminates the process and launches it again to attempt recovery (see 3.3 VPN Server Administration for details). The example below was actually runs on a particular Linux system so it may not appear the same on different Linux or other operating systems. In addition, in order to display multiple threads as multiple processes in the case of versions with old Linux kernels (i.e. versions not compatible with native threads), the actual vpnserver processes created may be more than those in the example below but this is a display issue and operation is in fact normal.
...
Although this only occurs rarely, in the event that the VPN Server process launched in User Mode goes out of control for some reason such as a hardware malfunction (a memory shortage, for instance) and is unable to be stopped by vpnserver /stop, first forcibly terminate the parent vpnserver process (process ID 1549 in the example above) by sending a signal to it using kill -KILL, then forcibly terminate the remaining process (process ID 1550 in the above example) by sending a signal to it with kill -KILL. Forcibly terminating the child process first may cause the parent process to determine that the child process terminated abnormally and launch it again. Depending on the system, killall -KILL vpnserver may enable the simultaneous termination of all vpnserver processes.
...
