sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-06 13:18:07 +03:00
Code
4e36eec244
samba-mirror/packaging/systemd/ctdb.service.in

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

20 lines
389 B
SYSTEMD
Raw Normal View History

packaging: Add systemd support Based on an original patch by Sumit Bose <sbose@redhat.com>. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit e43a4b7b69a21c4cec2453dcac436b64bf5d7f06)
2013-07-10 11:19:55 +04:00
[Unit]
Description=CTDB
systemd: Add documentation to Unit files BUG: https://bugzilla.samba.org/show_bug.cgi?id=12402 Signed-off-by: Mathieu Parent <math.parent@gmail.com> Reviewed-by: Andreas Schneider <asn@samba.org> Reviewed-by: Alexander Bokovoy <ab@samba.org>
2016-05-12 23:16:24 +03:00
Documentation=man:ctdbd(1) man:ctdb(7)
ctdb-packaging: Fix systemd network dependency https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ says: network.target has very little meaning during start-up. [...] Whether any network interfaces are already configured when it is reached is undefined. [...] network-online.target is a target that actively waits until the ne[t]work is "up", CTDB expects to be able to bind a socket to a node address and expects interfaces for public IP addresses to exist. CTDB also doesn't expect time to jump, so also wait until time is synchronised. BUG: https://bugzilla.samba.org/show_bug.cgi?id=12255 Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Steve French <sfrench@samba.org> Reviewed-by: Amitay Isaacs <amitay@gmail.com> Tested-by: Steve French <sfrench@samba.org>
2016-09-08 05:28:00 +03:00
After=network-online.target time-sync.target
packaging: move CTDB service file to top-level Signed-off-by: Vinit Agnihotri <vagnihotri@ddn.com> Reviewed-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2022-03-01 09:24:06 +03:00
ConditionFileNotEmpty=@CTDB_ETCDIR@/nodes
packaging: Add systemd support Based on an original patch by Sumit Bose <sbose@redhat.com>. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit e43a4b7b69a21c4cec2453dcac436b64bf5d7f06)
2013-07-10 11:19:55 +04:00
[Service]
Type=forking
LimitCORE=infinity
ctdb-config: Add default ctdb.sysconfig file, update ctdb.service Install ctdb.sysconfig in RPM. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-04-24 09:35:16 +03:00
LimitNOFILE=1048576
ctdb: increase TasksMax limit, the systemd default is just 512 In 2015 systemd introduced a TasksMax which limits the number of processes in a unit: https://lists.freedesktop.org/archives/systemd-devel/2015-November/035006.html The default of 512 may be too low in certain situations leading to vfork() failing with errno=EAGAIN when trying to spawn lock-helper processes. With the default for LockProcessesPerDB being 200 the increased TasksMax limit should cover the problematic scenario. Additional background: the failing vfork()s have been seen on production clusters and were tracked down to being logged in the context of ctdb calling tdb_repack(). Links: https://github.com/systemd/systemd/commit/9ded9cd14cc03c67291b10a5c42ce5094ba0912f https://www.suse.com/support/kb/doc/?id=000015901 https://success.docker.com/article/how-to-reserve-resource-temporarily-unavailable-errors-due-to-tasksmax-setting https://www.percona.com/blog/2019/01/02/tasksmax-another-setting-that-can-cause-mysql-error-messages/ Signed-off-by: Ralph Boehme <slow@samba.org> Reviewed-by: Martin Schwenke <martin@meltin.net> Autobuild-User(master): Martin Schwenke <martins@samba.org> Autobuild-Date(master): Wed May 13 13:30:12 UTC 2020 on sn-devel-184
2020-05-12 16:30:05 +03:00
TasksMax=4096
packaging: move CTDB service file to top-level Signed-off-by: Vinit Agnihotri <vagnihotri@ddn.com> Reviewed-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2022-03-01 09:24:06 +03:00
PIDFile=@CTDB_RUNDIR@/ctdbd.pid
ctdb-scripts: Drop uses of ctdbd_wrapper The only value this now provides is use of a notification script to log when start/stop are called. This was used for debugging strange start/stop failures, which have not been recently seen. Also, systemd does a good job of logging start/stop. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2022-02-01 00:28:47 +03:00
ExecStart=@SBINDIR@/ctdbd
ExecStop=@BINDIR@/ctdb shutdown
packaging: Add systemd support Based on an original patch by Sumit Bose <sbose@redhat.com>. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit e43a4b7b69a21c4cec2453dcac436b64bf5d7f06)
2013-07-10 11:19:55 +04:00
KillMode=control-group
Restart=no
[Install]
WantedBy=multi-user.target
Copy Permalink