Hi, Sven. On 08/02/17 14:37, Sven Hartge wrote:
>> In this case, it seems that the service file for systemd is created >> dynamically. Or I'm wrong? >> >> -------------------------------------------------------------------- >> root@conference:~# find / -name jitsi-videobridge.service >> /sys/fs/cgroup/systemd/system.slice/jitsi-videobridge.service >> /run/systemd/generator.late/jitsi-videobridge.service >> /run/systemd/generator.late/runlevel5.target.wants/jitsi-videobridge.service >> /run/systemd/generator.late/runlevel4.target.wants/jitsi-videobridge.service >> /run/systemd/generator.late/runlevel3.target.wants/jitsi-videobridge.service >> /run/systemd/generator.late/runlevel2.target.wants/jitsi-videobridge.service >> -------------------------------------------------------------------- > You can also generate override files for dynamically generated units by > creating /etc/systemd/system/jitsi-videobridge.service.d/configname.conf > > "configname" can be whatever you want. > > In this file you then put > > ,---- > | [Service] > | LimitNOFILE=65536 > `---- > > and do a "systemctl daemon-reload". > > If you now "systemctl cat jitsi-videobridge.service" you should get the > output of the generated file and your appended override config. Great! That worked! It seems that the only value specified in LimitNOFILE applies to both the soft and hard limit. Thank you very much for your reply. Kind regards, Daniel
signature.asc
Description: OpenPGP digital signature
