Re: cyrus 2.4.17 -- file descriptor limit set to -1?
On Thu, 2015-01-15 at 11:17 +, Geoff Winkless wrote: RLIM_INFINITY is defined as ~0ULL, at least on my system. If it's cast to a signed value, that will come out at -1, no? My problem with systemd isn't that it doesn't work, It works. it's that it's all-pervasive and viral, and forces people who've been using standard unix mechanisms for 20 years to learn something completely different for no visible concrete advantage. There are many advantages, but this is not the place to debate the much-debated systemd. Resource contol on modern LINUX systems is managed via cgroups. This was added to the kernel quite some time ago to avoid all the ulimit nonsense and concomitant hacks. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/ch01.html Systemd relies on cgroups. cgroups are a huge step forward and make administration much easier and more flexible. I do not know what distribution you are using but /etc/security/limits is generally still effective as well. If you want to run unlimited change it to: default: fsize = -1 - which has been the correct way to do this for a very long time. As a user rather than a sysadmin it If you are running an IMAP host then you are a sysadmin. -- Adam Tauno Williams mailto:awill...@whitemice.org GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
cyrus 2.4.17 -- file descriptor limit set to -1?
I'm firing up cyrus 2.4.17 for the first time on a new platform (Arch linux w/ systemd) and noticed the following error message (running journalctl -u cyrus-master): Jan 15 04:08:50 ibis cyrus/master[701]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Jan 15 04:08:50 ibis cyrus/master[701]: retrying with 4096 (current max) Apparently the cyrus master process is trying to set the file descriptor limit to -1? Is it even legal to use -1 as infinity in this context? According to the setrlimit man page: The soft limit is the value that the kernel enforces for the corresponding resource. The hard limit acts as a ceiling for the soft limit: an unprivileged process may only set its soft limit to a value in the range from 0 up to the hard limit, and (irreversibly) lower its hard limit. A privileged process (under Linux: one with the CAP_SYS_RESOURCE capability) may make arbitrary changes to either limit value. The value RLIM_INFINITY denotes no limit on a resource (both in the structure returned by getrlimit() and in the structure passed to setrlimit()). BTW, off topic and perhaps feeding some trolls, I'm really liking systemd so far; in part because it's alerting me to minor misconfiguration errors that I've had around for years but wasn't aware of. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: cyrus 2.4.17 -- file descriptor limit set to -1?
RLIM_INFINITY is defined as ~0ULL, at least on my system. If it's cast to a signed value, that will come out at -1, no? My problem with systemd isn't that it doesn't work, it's that it's all-pervasive and viral, and forces people who've been using standard unix mechanisms for 20 years to learn something completely different for no visible concrete advantage. As a user rather than a sysadmin it seems I have to spend most of my time learning new ways to do exactly the same things without gaining anything. Frankly I'm past the point where I want to fiddle with Linux for hours to make it do what I want. But that seems to be the Linux Way these days, see eg ip vs ifconfig, iptables vs ipchains, c c c. On 15 January 2015 at 11:04, Patrick Goetz pgo...@mail.utexas.edu wrote: I'm firing up cyrus 2.4.17 for the first time on a new platform (Arch linux w/ systemd) and noticed the following error message (running journalctl -u cyrus-master): Jan 15 04:08:50 ibis cyrus/master[701]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Jan 15 04:08:50 ibis cyrus/master[701]: retrying with 4096 (current max) Apparently the cyrus master process is trying to set the file descriptor limit to -1? Is it even legal to use -1 as infinity in this context? According to the setrlimit man page: The soft limit is the value that the kernel enforces for the corresponding resource. The hard limit acts as a ceiling for the soft limit: an unprivileged process may only set its soft limit to a value in the range from 0 up to the hard limit, and (irreversibly) lower its hard limit. A privileged process (under Linux: one with the CAP_SYS_RESOURCE capability) may make arbitrary changes to either limit value. The value RLIM_INFINITY denotes no limit on a resource (both in the structure returned by getrlimit() and in the structure passed to setrlimit()). BTW, off topic and perhaps feeding some trolls, I'm really liking systemd so far; in part because it's alerting me to minor misconfiguration errors that I've had around for years but wasn't aware of. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
