3 ms·
:/ I was hoping it would clarify why I have to look in so many places. Process can't fork? Better check * sysctl and /etc/sysctl.conf * ulimit (soft and har
by paulddraper 8y ago
:/ I was hoping it would clarify why I have to look in so many places.
Process can't fork?
Better check
* sysctl and /etc/sysctl.conf
* ulimit (soft and hard) and /etc/security/limits.conf
* systemd configuration, would could be in /etc/systemd/system, /run/systemd/system, /usr/lib/systemd/system, /usr/local/lib/systemd/system, or a half dozen other places
This isn't across a bunch of distros; this is all on the same Linux system.
And I guarantee this list isn't even complete.
Somebody is loving recreating what already exists.
- Nullabillity 8y ago> * systemd configuration, would could be in /etc/systemd/system, /run/systemd/system, /usr/lib/systemd/system, /usr/local/lib/systemd/system, or a half dozen other places `systemctl status blah.service` will tell you all the systemd unit files that configure the service, and `systemctl show blah.service` will show you the final config that is actually applied.
- paulddraper 8y agoYes, that save time, if the configuration in question is currently on a running machine.