Your message dated Tue, 22 Aug 2023 23:44:35 +0200
with message-id <3adde7ef-5d5d-422b-b40d-aca371868...@debian.org>
and subject line Re: PathModified in path activation propagates to containing
directory when file is deleted
has caused the Debian Bug report #876261,
regarding PathModified in path activation propagates to containing directory
when file is deleted
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
876261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 232-25+deb9u1
Severity: normal
Hello,
given this setup:
# cat beeponce.service
[Unit]
Description=Beeps
[Service]
Type=oneshot
ExecStart=/usr/bin/aplay /tmp/beep.wav
# cat beeponce.path
[Unit]
Description=Monitor /tmp/zz
[Path]
PathModified=/tmp/zz
This happens:
touch /tmp/zz # BEEP! (ok)
rm /tmp/zz # BEEP! (ok)
touch /tmp/foo # BEEP! (What??)
touch /tmp/foo # silence (ok)
touch /tmp/zz # BEEP! (ok)
touch /tmp/foo # silence (ok)
It looks like systemd is listening to events in the containing directory to
catch if the file is created, and after removing the file it accidentally
triggers on a directory event even if it's not about the file being monitored.
Enrico
-- Package-specific info:
-- System Information:
Debian Release: 9.1
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-3
ii libaudit1 1:2.6.7-2
ii libblkid1 2.29.2-1
ii libc6 2.24-11+deb9u1
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-4
ii libgcrypt20 1.7.6-2+deb9u2
ii libgpg-error0 1.26-2
ii libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-6
ii libkmod2 23-2
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.2+b1
ii libmount1 2.29.2-1
ii libpam0g 1.1.8-3.6
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3+b1
ii libsystemd0 232-25+deb9u1
ii mount 2.29.2-1
ii procps 2:3.3.12-3
ii util-linux 2.29.2-1
Versions of packages systemd recommends:
ii dbus 1.10.18-1
ii libpam-systemd 232-25+deb9u1
Versions of packages systemd suggests:
ii policykit-1 0.105-18
ii systemd-container 232-25+deb9u1
ii systemd-ui 3-4+b1
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.130
ii udev 232-25+deb9u1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 254.1-2
On Wed, 20 Sep 2017 11:42:58 +0200 Enrico Zini <enr...@debian.org> wrote:
Package: systemd
Version: 232-25+deb9u1
Severity: normal
Hello,
given this setup:
# cat beeponce.service
[Unit]
Description=Beeps
[Service]
Type=oneshot
ExecStart=/usr/bin/aplay /tmp/beep.wav
# cat beeponce.path
[Unit]
Description=Monitor /tmp/zz
[Path]
PathModified=/tmp/zz
This happens:
touch /tmp/zz # BEEP! (ok)
rm /tmp/zz # BEEP! (ok)
touch /tmp/foo # BEEP! (What??)
touch /tmp/foo # silence (ok)
touch /tmp/zz # BEEP! (ok)
touch /tmp/foo # silence (ok)
It looks like systemd is listening to events in the containing directory to
catch if the file is created, and after removing the file it accidentally
triggers on a directory event even if it's not about the file being monitored.
Seems to work as expected in sid, so closing for that version.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
