[Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

2017-07-21 Thread Dimitri John Ledkov
** No longer affects: systemd (Ubuntu Yakkety) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1686361 Title: systemd does not respect nofile ulimit when running in container To ma

[Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

2017-07-20 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-4ubuntu19 --- systemd (229-4ubuntu19) xenial; urgency=medium * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially revert, by removing ExecStart|StopPost lines, as these are not needed on xenial and generat

[Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

2017-06-22 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 232-21ubuntu4 --- systemd (232-21ubuntu4) zesty; urgency=medium * Cherrypick upstream commit to enable system use kernel maximum limit for RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361) * debian/tests/root-

[Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

2017-05-11 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 233-6ubuntu1 --- systemd (233-6ubuntu1) artful; urgency=medium Merge from Debian, existing changes: * ubuntu: udev.postinst preserve virtio interfaces names on upgrades, on s390x. New udev generates stable interface names on s390x k

[Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

2017-04-26 Thread Dimitri John Ledkov
** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: Confirmed ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: