After some search, i guess the pid=1 limits come from the nr_open now and the default nr_open come from linux code[0].
So there should be no way to change the pid=1 limit unless you re-compile your kernel with some code change. [0] https://github.com/torvalds/linux/blob/master/fs/file.c#L22-L27 On Tue, Oct 9, 2018 at 1:40 PM Jeffrey Zhang <[email protected]> wrote: > Thanks Richard, > > That explains why archlinux NOFILE is 1048576. archlinux is using systemd > 239.2-1 > > But it still can not explain where the pid=1 process limits come from? is > there any way to change it? > > On Tue, Oct 9, 2018 at 1:31 PM Richard W <[email protected]> wrote: > >> There's an issue on github on this: >> https://github.com/systemd/systemd/issues/6559 >> >> On Tue, Oct 9, 2018 at 9:42 AM Jeffrey Zhang <[email protected]> >> wrote: >> >>> hey guys, >>> >>> In the recently test, i found some interesting phenomenon. >>> >>> in systemd service, if i configure LimitNOFILE=infinity, it is not a >>> real infinity. the finally NOFILE will be 65536 ( on centos7 ) and 1048576 >>> ( on archlinux), and the pid=1 process also have the same value. >>> >>> So my question is, >>> >>> 1. where the pid=1 limits come from? because centos7 and archlinux are >>> different, so i guess this should be configurable or pre-compiled. >>> 2. is the inifinity equals pid=1 limits in default? >>> >>> -- >>> Regards, >>> Jeffrey Zhang >>> Blog: http://xcodest.me >>> _______________________________________________ >>> systemd-devel mailing list >>> [email protected] >>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> >> > > -- > Regards, > Jeffrey Zhang > Blog: http://xcodest.me > -- Regards, Jeffrey Zhang Blog: http://xcodest.me
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
