Bug 80341 - DOC: mention which LimitXYZ= map to shell ulimit switches
Summary: DOC: mention which LimitXYZ= map to shell ulimit switches
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-21 19:43 UTC by Yahel Zamir
Modified: 2014-11-30 19:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Yahel Zamir 2014-06-21 19:43:38 UTC
systemd documentation does not mention clearly what are the field names to replace  bash ulimit command:
·         LimitNOFILE= replaces “ulimit –n”
·         LimitMSGQUEUE= replaces “ulimit –q”
·         LimitCORE= replaces “ulimit –c”

The documentation just mentions the C functions, but systemd replaces mostly initialization shell scripts, therefore its documentation, at least some FAQ or other text, should mention its alternative for useful shell commands.

The same goes for other bash commands, such as "taskset".
Comment 1 Ronny Chevalier 2014-11-30 19:57:37 UTC
(In reply to Yahel Zamir from comment #0)
> systemd documentation does not mention clearly what are the field names to
> replace  bash ulimit command:
> ·         LimitNOFILE= replaces “ulimit –n”
> ·         LimitMSGQUEUE= replaces “ulimit –q”
> ·         LimitCORE= replaces “ulimit –c”
> 
> The documentation just mentions the C functions, but systemd replaces mostly
> initialization shell scripts, therefore its documentation, at least some FAQ
> or other text, should mention its alternative for useful shell commands.
> 
> The same goes for other bash commands, such as "taskset".
Hi,

man page improved for equivalence between Limit* and ulimit: http://cgit.freedesktop.org/systemd/systemd/commit/?id=b8825fff7bf153ea9f17c46a40278df2e780829d

As for taskset/CPUAffinity= the equivalence is straightforward ?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.