https://blog.csdn.net/wait2023zh-cnhttps://blog.csdn.net/https://blog.csdn.net/wait2023/article/details/129211769https://blog.csdn.net/wait2023/article/details/129211769wait2023Sat, 25 Feb 2023 09:22:00 +0800https://blog.csdn.net/wait2023/article/details/128808013https://blog.csdn.net/wait2023/article/details/128808013wait2023Mon, 30 Jan 2023 20:04:25 +0800https://blog.csdn.net/wait2023/article/details/128807989https://blog.csdn.net/wait2023/article/details/128807989wait2023Mon, 30 Jan 2023 20:01:28 +0800https://blog.csdn.net/wait2023/article/details/128766993https://blog.csdn.net/wait2023/article/details/128766993wait2023Thu, 26 Jan 2023 19:08:32 +0800https://blog.csdn.net/wait2023/article/details/128766000https://blog.csdn.net/wait2023/article/details/128766000wait2023Thu, 26 Jan 2023 16:13:02 +0800https://blog.csdn.net/wait2023/article/details/128765948https://blog.csdn.net/wait2023/article/details/128765948wait2023Thu, 26 Jan 2023 16:09:05 +0800https://blog.csdn.net/wait2023/article/details/128647728https://blog.csdn.net/wait2023/article/details/128647728wait2023Wed, 11 Jan 2023 17:02:56 +0800 0，就是给pid对应的进程发信号pid =0，给调用该方法的进程的同组进程发送sig信号，即组内广播pid = -1 ，sig会被发送给当前进程能够发送信号的所有进程，除了init进程pid < -1，会将sig发送给进程组ID为-pid的进程sig = 0时为检测pid进程或-pid进程组是否存在返回值：成功返回0失败返回-1，同时设置errnoraise(3) 给当前进程发送一个信号，自己给自己发。]]>https://blog.csdn.net/wait2023/article/details/128635845https://blog.csdn.net/wait2023/article/details/128635845wait2023Tue, 10 Jan 2023 20:28:40 +0800https://blog.csdn.net/wait2023/article/details/128584702https://blog.csdn.net/wait2023/article/details/128584702wait2023Fri, 06 Jan 2023 20:44:41 +0800https://blog.csdn.net/wait2023/article/details/128576921https://blog.csdn.net/wait2023/article/details/128576921wait2023Fri, 06 Jan 2023 12:53:09 +0800https://blog.csdn.net/wait2023/article/details/128571105https://blog.csdn.net/wait2023/article/details/128571105wait2023Thu, 05 Jan 2023 22:08:01 +0800https://blog.csdn.net/wait2023/article/details/128571048https://blog.csdn.net/wait2023/article/details/128571048wait2023Thu, 05 Jan 2023 22:06:13 +0800https://blog.csdn.net/wait2023/article/details/127338583https://blog.csdn.net/wait2023/article/details/127338583wait2023Sat, 15 Oct 2022 18:31:21 +0800https://blog.csdn.net/wait2023/article/details/125351238https://blog.csdn.net/wait2023/article/details/125351238wait2023Sat, 18 Jun 2022 20:20:11 +0800https://blog.csdn.net/wait2023/article/details/125130069https://blog.csdn.net/wait2023/article/details/125130069wait2023Sun, 05 Jun 2022 11:25:10 +0800https://blog.csdn.net/wait2023/article/details/125129267https://blog.csdn.net/wait2023/article/details/125129267wait2023Sun, 05 Jun 2022 10:15:09 +0800https://blog.csdn.net/wait2023/article/details/125089276https://blog.csdn.net/wait2023/article/details/125089276wait2023Wed, 01 Jun 2022 19:49:37 +0800https://blog.csdn.net/wait2023/article/details/125072824https://blog.csdn.net/wait2023/article/details/125072824wait2023Tue, 31 May 2022 20:26:30 +0800https://blog.csdn.net/wait2023/article/details/124980041https://blog.csdn.net/wait2023/article/details/124980041wait2023Thu, 26 May 2022 10:32:06 +0800https://blog.csdn.net/wait2023/article/details/124977919https://blog.csdn.net/wait2023/article/details/124977919wait2023Thu, 26 May 2022 10:05:40 +0800