<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">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?</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">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.</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">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. <br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 15 January 2015 at 11:04, Patrick Goetz <span dir="ltr"><<a href="mailto:pgoetz@mail.utexas.edu" target="_blank">pgoetz@mail.utexas.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm firing up cyrus 2.4.17 for the first time on a new platform (Arch<br>
linux w/ systemd) and noticed the following error message (running<br>
journalctl -u cyrus-master):<br>
<br>
Jan 15 04:08:50 ibis cyrus/master[701]: setrlimit: Unable to set file<br>
descriptors limit to -1: Operation not permitted<br>
Jan 15 04:08:50 ibis cyrus/master[701]: retrying with 4096 (current max)<br>
<br>
<br>
Apparently the cyrus master process is trying to set the file descriptor<br>
limit to -1? Is it even legal to use -1 as infinity in this context?<br>
According to the setrlimit man page:<br>
------------------------------------<br>
The soft limit is the value that the kernel enforces for the<br>
corresponding resource. The hard limit acts as a ceiling for the soft<br>
limit: an unprivileged process may only set its soft limit to a value in<br>
the range from 0 up to the hard limit, and (irreversibly) lower its hard<br>
limit. A privileged process (under Linux: one with the CAP_SYS_RESOURCE<br>
capability) may make arbitrary changes to either limit value.<br>
<br>
The value RLIM_INFINITY denotes no limit on a resource (both in the<br>
structure returned by getrlimit() and in the structure passed to<br>
setrlimit()).<br>
------------------------------------<br>
<br>
BTW, off topic and perhaps feeding some trolls, I'm really liking<br>
systemd so far; in part because it's alerting me to minor<br>
misconfiguration errors that I've had around for years but wasn't aware of.<br>
<br>
----<br>
Cyrus Home Page: <a href="http://www.cyrusimap.org/" target="_blank">http://www.cyrusimap.org/</a><br>
List Archives/Info: <a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/</a><br>
To Unsubscribe:<br>
<a href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus" target="_blank">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a><br>
</blockquote></div><br></div>