Am 19.09.2011 20:48, schrieb Lennart Poettering:
> On Mon, 19.09.11 20:42, Reindl Harald ([email protected]) wrote:
>>> limits.conf is generally only applied to logins, not to system services
>>
>> i remeber that was the reaso include it in the /etc/initd./service because
>> started processes from here should use the limits from the
>> parent-shell
> 
> systemd invokes all services in clean defined execution contexts with
> reset resource limits. This problem should not exist on systemd hence.

you missunderstood me

the problem was "limuts.conf" ignored fro mysqld and solved by the
init-shellscript using ulimit - so with systemd a problem comes back

>> but why is "limits.conf" ignored by services?
> 
> It's the configuration file of pam_limits, and since PAM is for user
> authentication and session management and mysql is a service we don't
> invoke it

bad - in my opinion "limts.conf" would be the right place from
the user-side becasue it affects users/groups and finally services
are running as a user/group - so sould be there not exist one
central point of configuration?


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to