samba-mirror

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 17:19:55 +10:00

[Unit]

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 22:16:24 +02: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 12:28:00 +10:00

								After=network-online.target time-sync.target
							

ctdb-config: depend on /etc/ctdb/nodes file BUG: https://bugzilla.samba.org/show_bug.cgi?id=14017 CTDB should start as a disabled unit (systemd) in most of the distributions and, when trying to enable it for the first time, user should get an unconfigured, or similar, error. Depending on /etc/ctdb/nodes file will give a clear direction to final user on what is needed in order to get cluster up and running. It should work like previous ENABLED=NO variables in SySV like initialization scripts. Signed-off-by: Rafael David Tinoco <rafaeldtinoco@ubuntu.com> Reviewed-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>

2019-06-27 20:12:25 +00:00

								ConditionFileNotEmpty=/etc/ctdb/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 17:19:55 +10:00

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 16:35:16 +10: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 15:30:05 +02:00

								TasksMax=4096
							

initscript: Update systemd configuration to put PID file in /run/ctdb Elsewhere we're moving the socket to /var/run/ctdb. We might end up with PID files and sockets for other daemons later, so let's call the directory "ctdb" instead of "ctdbd". Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit b63f6fd2d295c8e18cbf3420ab05fce07b727f31)

2013-10-23 11:28:26 +11:00

								PIDFile=/run/ctdb/ctdbd.pid
							

ctdb-scripts: Drop PID file argument from wrapper Use the default compile-time PID file. Use a CTDB_PIDFILE environment variable when testing. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>

2018-03-05 21:02:40 +11:00

								ExecStart=/usr/sbin/ctdbd_wrapper start
							

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 17:19:55 +10:00

								KillMode=control-group
							

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 17:19:55 +10: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 22:16:24 +02: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 12:28:00 +10:00			`After=network-online.target time-sync.target`
ctdb-config: depend on /etc/ctdb/nodes file BUG: https://bugzilla.samba.org/show_bug.cgi?id=14017 CTDB should start as a disabled unit (systemd) in most of the distributions and, when trying to enable it for the first time, user should get an unconfigured, or similar, error. Depending on /etc/ctdb/nodes file will give a clear direction to final user on what is needed in order to get cluster up and running. It should work like previous ENABLED=NO variables in SySV like initialization scripts. Signed-off-by: Rafael David Tinoco <rafaeldtinoco@ubuntu.com> Reviewed-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> 2019-06-27 20:12:25 +00:00			`ConditionFileNotEmpty=/etc/ctdb/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 17:19:55 +10: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 16:35:16 +10: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 15:30:05 +02:00			`TasksMax=4096`
initscript: Update systemd configuration to put PID file in /run/ctdb Elsewhere we're moving the socket to /var/run/ctdb. We might end up with PID files and sockets for other daemons later, so let's call the directory "ctdb" instead of "ctdbd". Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit b63f6fd2d295c8e18cbf3420ab05fce07b727f31) 2013-10-23 11:28:26 +11:00			`PIDFile=/run/ctdb/ctdbd.pid`
ctdb-scripts: Drop PID file argument from wrapper Use the default compile-time PID file. Use a CTDB_PIDFILE environment variable when testing. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> 2018-03-05 21:02:40 +11:00			`ExecStart=/usr/sbin/ctdbd_wrapper start`
			`ExecStop=/usr/sbin/ctdbd_wrapper stop`
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 17:19:55 +10:00			`KillMode=control-group`
			`Restart=no`

			`[Install]`
			`WantedBy=multi-user.target`

20 lines 401 B SYSTEMD Raw Normal View History Unescape Escape

20 lines

401 B

SYSTEMD

Raw Normal View History