Hi Bri,
Right, the PPID of the parent process should be always 1. However, it sounds to me the PPID of the child processes should be the stunnel parent PID. With my example, if I kill PID 10764, all the stunnel processes will be gone. So I expect that's the parent, then the others should have PPID "10764". Isn't it?
UID PID PPID C STIME TTY TIME CMD philwong 10759 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10760 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10761 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10762 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10763 1 0 16:27 pts/78 00:00:00 stunnel self.conf philwong 10764 1 0 16:27 ? 00:00:00 stunnel self.conf
Regards, Philip
On 9 Apr, 2012, at 12:38 AM, Bri Hatch wrote:
On Sat, Apr 7, 2012 at 3:38 AM, Philip Wong hochit@gmail.com wrote:
Hi Thomas,
Thanks for your reply.
Can we set child processes with correct PPID?
PPID is the parent process ID number, i.e. the PID of the process that ran you. When I am in bash and run 'ls', the PPID of ls is my bash shell.
This has nothing to do with the userid of any of these processes.
When your PPID is 1 that means that your parent has exited, and you have been inherited by the init process (process ID 1).
Sounds like you killed the parent stunnel process exited but the children continued on because they weren't done handling their requests. This is not abnormal.
-- Bri Hatch, Systems and Security Engineer. http://www.ifokr.org/bri/
"Quite mad, they say. It is good that Zathras does not mind. He's even grown to like it. Oh yes."