Bug#1100399: incron: Incron should not get triggered by its own child p
From
Patrik Schindler@21:1/5 to
All on Thu Mar 13 12:30:01 2025
Package: incron
Version: 0.5.12-4
Severity: normal
When incron is tasked to watch something, and the program part of the incrontab entry triggers the same event being watched, incron gets stuck in an endless loop.
Example:
/mydir IN_ATTRIB chmod g+w $@/$#
Then create a file:
touch /mydir/myfile
And run chmod on it:
chmod 640 /mydir/myfile
Adding ",loopable=0" doesn't change this behavior.
Incron should generally exclude events being triggered by its childs from being considered as trigger.
-- System Information:
Debian Release: 12.9
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-31-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages incron depends on:
ii adduser 3.134
ii init-system-helpers 1.65.2
ii libc6 2.36-9+deb12u9
ii libgcc-s1 12.2.0-14
ii libstdc++6 12.2.0-14
incron recommends no packages.
incron suggests no packages.
-- Configuration Files:
/etc/incron.allow [Errno 2] No such file or directory: '/etc/incron.allow' /etc/incron.deny [Errno 2] No such file or directory: '/etc/incron.deny'
-- no debconf information
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)