提供在 RISC-V 架构上的 lvmlockd.service · Pull Request !111 · src-openEuler/lvm2

我们发现在 RISC-V 架构上的并没有 lvmlockd.service 。
经过查询 build log, 发现是在 build 的时候并未 build lvmlockd。log 如下：

```
[  617s] checking whether to use device-mapper... yes
[  617s] checking whether to build lvmpolld... yes
[  617s] checking whether to build lvmlockdsanlock... no
[  617s] checking whether to build lvmlockddlm... no
[  617s] checking whether to build lvmlockddlmcontrol... no
[  617s] checking whether to build lvmlockdidm... no
[  617s] checking whether to build lvmlockd... no
[  617s] checking defaults for use_lvmpolld... 1
[  617s] checking whether to build notifydbus... yes
```

本 pr 使得 lvm2 在 RISC-V 架构上提供 lvmlockd.service 。成后的 log 如下：

```
[  307s] checking whether to use device-mapper... yes
[  307s] checking whether to build lvmpolld... yes
[  307s] checking whether to build lvmlockdsanlock... yes
[  307s] checking for libsanlock_client >= 3.3.0... yes
[  307s] checking whether to build lvmlockddlm... no
[  307s] checking whether to build lvmlockddlmcontrol... no
[  307s] checking whether to build lvmlockdidm... no
[  307s] checking whether to build lvmlockd... yes
[  307s] checking defaults for use_lvmlockd... 1
[  307s] checking defaults for use_lvmpolld... 1
[  307s] checking whether to build notifydbus... yes
[  308s] checking for systemd/sd-journal.h... yes
```

经过测试，打出来的 lvmlockd.service 是可以正常运行的。

```
systemctl status lvmlockd
● lvmlockd.service - LVM lock daemon
     Loaded: loaded (/usr/lib/systemd/system/lvmlockd.service; disabled; preset: disabled)
     Active: active (running) since Mon 2023-09-11 17:50:41 CST; 9s ago
       Docs: man:lvmlockd(8)
   Main PID: 776 (lvmlockd)
      Tasks: 3 (limit: 101828)
     Memory: 520.0K
     CGroup: /system.slice/lvmlockd.service
             └─776 /usr/sbin/lvmlockd --foreground
```

src-openEuler/lvm2 .gitee-modal { width: 500px !important; }

搜索帮助

src-openEuler/lvm2