Comment # 21 on bug 1165780 from
(In reply to Franck Bui from comment #17)
> (In reply to Karl Mistelberger from comment #16)
> > Yet another claim which is not supported by evidence. I reiterate: removing
> > After=local-fs.target from unit btrfsmaintenance-refresh.path results in
> > btrfsmaintenance-refresh.service being triggered before local-fs.target is
> > reached. This has been verified on one of my machines and has been confirmed
> > independently by several users at https://forums.opensuse.org/forum.php,
> 
> I didn't say that your workaround has no effect, I was just pointing out
> that it doesn't look correct.

systemd was updated since I made the changes to btrfsmaintenance-refresh.path.
Current  systemd-244-3.1 no longer reloads during boot.

Changes are now for btrfsmaintenance moved from sysconfig to default: 

erlangen:~ # systemd-delta -t overridden 
[OVERRIDDEN] /etc/systemd/system/btrfsmaintenance-refresh.path ���
/usr/lib/systemd/system/btrfsmaintenance-refresh.path

--- /usr/lib/systemd/system/btrfsmaintenance-refresh.path       2019-06-24
21:56:02.000000000 +0200
+++ /etc/systemd/system/btrfsmaintenance-refresh.path   2020-04-17
04:07:23.157871476 +0200
@@ -1,8 +1,9 @@
 [Unit]
-Description=Watch /etc/sysconfig/btrfsmaintenance
+Description=Watch /etc/default/btrfsmaintenance
+After=local-fs.target

 [Path]
-PathChanged=/etc/sysconfig/btrfsmaintenance
+PathChanged=/etc/default/btrfsmaintenance

 [Install]
 WantedBy=multi-user.target


With the above btrfsmaintenance-refresh.service runs only when
/etc/default/btrfsmaintenance actually changes.


You are receiving this mail because: