Table of contents
Combined revision comparison
...
- Installing the Windows version SoftEther VPN Server from the installer results in the installation of the Service Mode and automatic initiation of its operation as a background service. For details, please refer to
#7.2Install on Windows and Initial Configurations#.. - In order to install the SoftEther VPN Server in Service Mode on the Linux version or other UNIX versions, it is necessary to register it on the system as a daemon process. For details, please refer to
#7.3Install on Linux and Initial Configurations#..
...
Please refer to # 7.3Install on Linux and Initial Configurations# for details on installing and launching the Linux and other UNIX versions of the SoftEther VPN Server in Service Mode.
...
As described in #7.3Install on Linux and Initial Configurations#, , daemonizing and using the vpnserver process in UNIX operating systems is simply a matter of registering it so as to instruct the operating system's startup script to call up vpnserver start. Even when running the VPN Server in Service Mode, something equivalent to the procedure described here is automatically performed by a system with root authority so there is fundamentally no difference. Accordingly, the items described below also apply generally to the daemonized VPN Server.
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#3.3.12# 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.
...
Version from 18:53, 3 Mar 2013
...
- Installing the Windows version SoftEther VPN Server from the installer results in the installation of the Service Mode and automatic initiation of its operation as a background service. For details, please refer to
#7.2#. - In order to install the SoftEther VPN Server in Service Mode on the Linux version or other UNIX versions, it is necessary to register it on the system as a daemon process. For details, please refer to
#7.3#.
...
Please refer to #7.3# for details on installing and launching the Linux and other UNIX versions of the SoftEther VPN Server in Service Mode.
...
As described in #7.3#, daemonizing and using the vpnserver process in UNIX operating systems is simply a matter of registering it so as to instruct the operating system's startup script to call up vpnserver start. Even when running the VPN Server in Service Mode, something equivalent to the procedure described here is automatically performed by a system with root authority so there is fundamentally no difference. Accordingly, the items described below also apply generally to the daemonized VPN Server.
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.12# 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.
...
Version as of 16:31, 4 Mar 2013
...
- Installing the Windows version SoftEther VPN Server from the installer results in the installation of the Service Mode and automatic initiation of its operation as a background service. For details, please refer to 7.2Install on Windows and Initial Configurations.
- In order to install the SoftEther VPN Server in Service Mode on the Linux version or other UNIX versions, it is necessary to register it on the system as a daemon process. For details, please refer to 7.3Install on Linux and Initial Configurations.
...
Please refer to 7.3Install on Linux and Initial Configurations for details on installing and launching the Linux and other UNIX versions of the SoftEther VPN Server in Service Mode.
...
As described in 7.3Install on Linux and Initial Configurations, daemonizing and using the vpnserver process in UNIX operating systems is simply a matter of registering it so as to instruct the operating system's startup script to call up vpnserver start. Even when running the VPN Server in Service Mode, something equivalent to the procedure described here is automatically performed by a system with root authority so there is fundamentally no difference. Accordingly, the items described below also apply generally to the daemonized VPN Server.
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.
...
