Debian Codegraph @

debian/NEWS

raw
1 multipath-tools (0.9.8-1) unstable; urgency=medium
2
3 Socket activation as introduced in 0.9.4-6 was turned off again,
4 as upstream does not support it and claims it does not work.
5
6 Please make sure you have multipathd.service enabled:
7
8 systemctl enable multipathd.service
9
10 -- Chris Hofstaedtler <[email protected]> Thu, 13 Jun 2024 02:39:11 +0200
11
12 multipath-tools (0.9.4-7) unstable; urgency=medium
13
14 Booting from multipathed devices has significantly changed. It is recommended
15 testing your specific setup still boots properly, if you rely on this.
16
17 SysV init scripts have been removed, as they may clash with socket activation
18 and upgrade scenarios, especially when multipathd itself is not needed.
19
20 -- Chris Hofstaedtler <[email protected]> Sat, 11 Nov 2023 00:41:23 +0100
21
22 multipath-tools (0.9.4-6) unstable; urgency=medium
23
24 The systemd service for multipathd is now entirely socket-activated. On
25 new installations without any multipath device present in the system,
26 only multipathd.socket will be enabled and active. If there are
27 multipath devices available, then multipath.service will be activated (but
28 not enabled).
29
30 If you are upgrading from an existing installation and would like to use
31 socket activation from now on, please manually disable
32 multipathd.service and enable multipathd.socket:
33
34 systemctl disable multipathd.service
35 systemctl enable multipathd.socket
36
37 However, please keep in mind that socket activation does NOT work if
38 your root partition is located on a multipath device (in other words,
39 if the multipath-tools-boot package is installed). If that is your
40 case, then keep multipathd.service enabled:
41
42 systemctl enable multipathd.service
43
44 -- Sergio Durigan Junior <[email protected]> Sun, 15 Oct 2023 22:25:37 -0400
45
46 multipath-tools (0.7.7-1) unstable; urgency=medium
47
48 systemd support is well integrated for multipath-tools now. The old
49 initscripts are still provided and will be supported on a best effort basis
50 but users are advised to move to a systemd based setup
51
52 -- Ritesh Raj Sarraf <[email protected]> Sun, 07 Oct 2018 20:16:36 +0530
53
54 multipath-tools (0.5.0-4) unstable; urgency=medium
55
56 The systemd support has been dropped.
57
58 Device Mapper multipath is a core component in the SAN Stack. The
59 flexibility provided by shell init scripts were flexible. With
60 systemd, it is not the same anymore. We sure can create shell scripts
61 and pass it to systemd to run, but then it forfeits the philosophy of
62 systemd that "shell is evil". So rather that passing shell units to
63 systemd, we'll let systemd run this service in SysV compatibility
64 mode.
65
66 -- Ritesh Raj Sarraf <[email protected]> Fri, 05 Sep 2014 18:03:12 +0530
67
68 multipath-tools (0.4.7-2) unstable; urgency=low
69
70 udev, which provides scsi_id, moved the binary to /lib/udev.
71 The old name will stop working in the future.
72
73 The default config now uses /lib/udev/scsi_id. And you have to
74 update /etc/multipath.conf by hand to reflect the new location.
75
76 -- Bastian Blank <[email protected]> Wed, 29 Mar 2006 12:08:32 +0200
77
78 multipath-tools (0.4.5-1) unstable; urgency=low
79
80 This version removes creation of devices via udev in /dev. All
81 device-mapper devices are created by libdevmapper in /dev/mapper.
82
83 To readd the creation of devices in /dev, add the following line to
84 the udev rules (e.g. /etc/udev/rules.d/multipath.rules):
85 KERNEL=="dm-[0-9]*", PROGRAM="/sbin/devmap_name %M %m", NAME="%k", SYMLINK="%c", OPTIONS+="last_rule"
86
87 -- Bastian Blank <[email protected]> Mon, 19 Sep 2005 15:03:31 +0200
88