[RFC][PATCH] Do not set /proc inode->pid for non-pid-related
inodes
Cedric Le Goater
clg at fr.ibm.com
Thu Mar 22 07:49:54 PDT 2007
>>From sysvinit src/init.c:main
>> /*
>> * Is this telinit or init ?
>> */
>> isinit = (getpid() == 1);
>> for (f = 1; f < argc; f++) {
>> if (!strcmp(argv[f], "-i") || !strcmp(argv[f], "--init"))
>> isinit = 1;
>> break;
>> }
>> if (!isinit) exit(telinit(p, argc, argv));
>>
ok thanks for looking. I guess this is the end of the discussion on
pid == 1 :)
> [ snip ]
>
> Back to the main subject I still don't understand the idea of running
> a kernel daemon as pid == 1. What would that buy us?
mostly a child reaper when there are no /sbin/init but its pid cannot
be 1.
C.
More information about the Containers
mailing list