Hello,
does systemd take care of /etc/security/limits.conf ?
If i create a service-unit in /etc/systemd/system, enable it, which starts a script in /etc/init.d/ , the limits in /etc/security/limits.conf are ignored.
ulimit asks for the values of /etc/security/limits.conf, not for the values of the service-unit.
How can i ask for the values of my service-unit?
Best regards
We ask for the openSUSE version you use right when you start a new thread. There are the supported versions to choose from and the item OTHER VERSION when you are still running an unsupported version. We hope that the fact that that is the very first thing we ask signals people that when they choose other version, they should explain which one as the very first information in their thread.
Specially because OTHER VERSION can include very old versions of openSUSE or even SuSE, this information is important to your potential helpers. I hope you understand now why we ask this and please explain what you run.
ok, this is openSUSE 42.x, but also a general question.
Best regards
Not too general. You are talking about systemd and about /etc/init.d so people can easily get confused if you run a SysVinit or Systemd system, or that you are confused yourself about what belongs to your system.
Specialy because they will most probably come to the conclusion that you do NOT run Leap 42.2 or 42.3, because you say OTHER VERSION.
It is always nice to inform your potential helpers about your situation. Playing hide and seek is IMHO not something that will inspire people to help.
And as said, the staff here, getting very tired by asking again and again people what they are running (because many seem to think that the others here are clairvoyant or just being uneasy about how to formulate their request), introduced that menu. And it works in most cases. Either by direct choice, or it inspired people to mention this in their threads.
Although I haven’t modified this file for my own use,
A quick read about limits.conf suggests that it has little to do with any script you might write for any purpose…
It’s used to configure the pam_limits module.
So, unless your script hooks through that module, your script won’t affect anything having to do with the limits.conf file.
This is clearly stated in the MAN page
https://linux.die.net/man/5/limits.conf
You may find the ArchWiki about this topic useful for whatever you’re doing
https://wiki.archlinux.org/index.php/Limits.conf
This is all based on general principles.
If you have further questions, it’s likely you’ll have to post details about what your script is doing (particularly if it’s supposed to be managed by ulimits in some special way).
For now, I don’t see this as having anything to do with systemd but more likely what your script does and how it’s being done.
After a few more seconds’ thought, probably the more practical approach is to modify limits.conf according to the examples in the links I provided, then run your script in the appropriate security context for your new rules to apply.
TSU