<div dir="ltr"><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Jan 24, 2025 at 10:56 AM Windl, Ulrich <<a href="mailto:u.windl@ukr.de">u.windl@ukr.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-4708800898548097110">
<div lang="DE">
<div class="m_-4708800898548097110WordSection1">
<p class="MsoNormal">Hi!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span lang="EN-US">Debugging some backup issue I noticed that systemd announced “Starting Update system wide CA certificates...” multiple times during backup.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">As I was sure no new certificates were installed I checked the unit; it contains:<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"># /usr/lib/systemd/system/ca-certificates.path<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">[Unit]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Description=Watch for changes in CA certificates<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">After=local-fs.target<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">[Path]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Unit=ca-certificates.service<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">PathExists=/etc/pki/trust/.updated<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">PathChanged=/usr/share/pki/trust<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">PathChanged=/usr/share/pki/trust/anchors<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">PathChanged=/usr/share/pki/trust/blacklist<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">PathChanged=/etc/pki/trust<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">PathChanged=/etc/pki/trust/anchors<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">PathChanged=/etc/pki/trust/blacklist<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">[Install]<u></u><u></u></span></p>
<div style="border-width:medium medium 1pt;border-style:none none solid;border-color:currentcolor currentcolor windowtext;padding:0cm 0cm 1pt">
<p class="MsoNormal" style="border:medium;padding:0cm"><span lang="EN-US">WantedBy=default.target<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">When checking all the directories, I found no “change” there, but (old bug!):<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">The backup software tried to reset the file’s access time after backing up a file, so the inode modification time will be changed. Like this:</span></p></div></div></div></blockquote><div><br></div><div>The backup software should learn to open files with O_NOATIME...<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-4708800898548097110"><div lang="DE"><div class="m_-4708800898548097110WordSection1"><p class="MsoNormal"><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"># stat /etc/pki/trust/blacklist/<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> File: /etc/pki/trust/blacklist/<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"> Size: 0 Blocks: 0 IO Block: 4096 directory<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Device: 23h/35d Inode: 15384 Links: 1<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Access: 2025-01-24 09:44:43.086125631 +0100<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Modify: 2024-04-17 17:00:10.000000000 +0200<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Change: 2025-01-24 09:44:42.974123978 +0100<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Birth: 2024-11-12 09:04:58.891998036 +0100<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">So the directory was not modified in the sense of a content change.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">I wonder: Is systemd doing “the correct thing” for PathChanged=?</span></p></div></div></div></blockquote><div><br></div><div>I think that's what PathChanged= is documented to do, it reacts to all inotify events that indicate a change, including IN_ATTRIB – not specifically "contents".<br></div></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">Mantas Mikulėnas</div></div></div>