This was reported upstream as https://github.com/ar-/incron/issues/52
** Bug watch added: github.com/ar-/incron/issues #52
https://github.com/ar-/incron/issues/52
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is probably solved in all supported releases, as bionic uses
0.5.10-3build1, and 0.5.10 is apparently not affected.
That being said, I am experiencing a similar bug with bionic in a Docker
container, where incrond itself becomes a zombie process (and therefore
stops working).
--
You
There are some serious bugs in incron.
It should probably be deprecated and removed from the repos for security
reasons.
* https://github.com/ar-/incron/issues/67
* https://github.com/ar-/incron/issues/72
* https://github.com/ar-/incron/issues/68
** Bug watch added:
Assuming this is about Debian #930526, this is reportedly fixed in
0.5.12-2, and therefore in all releases except bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823490
Title:
Incron causes
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: incron (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823490
Title:
Given how this package is not getting much love, I switched to using systemd's
systemd.path functionality.
Very briefly:
root@veeta:/etc/systemd/system>cat gsker-temptrax.path
[Path]
PathChanged= /var/www/gsker/weather/temptrax.log
[Install]
WantedBy=default.target
Okay I see the git repo that this descends from,
https://github.com/ar-/incron, has this fix and several others. And I
see that the upstream is the debian package. How do we go about getting
the whole chain updated?
This bug was fixed back in Oct of 2017.
