On Thu, 2 Mar 2023 21:42:50 -0800 (PST), "
hongy...@gmail.com"
<
hongy...@gmail.com> wrote:
>
>They have the same pgid, sid, and sgid, as shown below:
>
>werner@X10DAi:~$ ps xao pid,ppid,pgid,sid,sgid,command | grep ' -l 10014' |grep -v grep
> 68311 67948 67948 64750 1000 sslocal -c /home/werner/Public/anti-gfw/conf/ssr2json/ssr/US_ssr_eebzkdao.nodelist.xyz_1381_1421cc147ea4bb31049aea01851aac7e.json -l 10014
> 68318 68311 67948 64750 1000 sslocal -c /home/werner/Public/anti-gfw/conf/ssr2json/ssr/US_ssr_eebzkdao.nodelist.xyz_1381_1421cc147ea4bb31049aea01851aac7e.json -l 10014
So, process 68318 was started by 68311.
This is a common construct:
The parent process (68311 in this case) does not handle
anything, it just spawns a child process (68318). That child
does the heavy lifting. If the child crashes, the parent spawns
a new one. In that case the child listens on the port.
There are other constructs, where the parent listens on the port
and spawns one or more child ("worker") processes to handle
incomin requests. The parent just mamages the request queue.
I don't know what happens here. As I said before, you have to
consult the sslocal documentation.
Ok, enough keywords there for you to search for mor elaborate
descriptions.
--
Kees Nuyt