you are simply wrong here and should blame your distribution for such an
old systemd which still links to the devel mailing list just because a
random service fails
in case of "Failed to start Tracker metadata" systemd is only the messenger
Am 10.10.18 um 00:33 schrieb [email protected]:
> sal
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
Hi,
is there a reliable way to check from a shell script that udevd is
running and able to serve request?
Say you want to run "udevadm trigger" but only if udevd is actually
able to process that request.
There is a udev_ctrl_send_ping() function, which looks like it could
be perhaps used for thos
On Di, 09.10.18 13:40, 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?
systemd whe
6 octobre 2018 14:22 "Lennart Poettering" a écrit:
> On Sa, 15.09.18 22:32, Baudouin Feildel ([email protected]) wrote:
>
> (Sorry for not responding more timely, I have been travelling and am
> still catching up with all the email)
No problem, we are all busy with tons of emails thos
