Hi, Am Montag, den 28.09.2015, 20:27 +0200 schrieb Joachim Breitner: > local-apt-repository ships with the following file: > > $ cat /lib/systemd/system/local-apt-repository.path > [Path] > PathChanged=/srv/local-apt-repository > > [Install] > WantedBy=paths.target > > If a process opens a not-yet-existing file in /srv/local-apt-repository, > starts writing and eventually closes it that systemd would activate the > corresponding service only after the close – at least that is my reading > of systemd.path(5). > > This can be reproduced by installing local-apt-repository, and running > > $ pv -L 100 < .../some.deb > /srv/local-apt-repository/some.deb > > and observing in the journal that dpkg-deb complains about an invalid > file. > > Is the documentation misleading me here, or is there a bug? > > If it is not a bug: Would it be possible to provide the behaviour that > was hoping for here?
I should add that it seems that changing an _existing_ file does, as documented, not cause the trigger to fire, only the creation of a new file. So I would assume that it is actually the change to the directory that causes the unwanted, first firing. Not sure if this is even fixable, i.e. whether systemd can detect that a newly created file was just opened for writing. Greetings, Joachim -- -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part