El 18/03/13 14:56, Britton Kerin escribió:
My service needs reasonably continuous mtimes on files.
That is the source of the problem, anything needing continuous mtimes is
operating under a broken assumption.
- You have timezone changes and leap seconds.
- You have machines that either by design or by error have a broken or
absent hardware clock (the raspberry pi for example, has no rtc)
- NTP takes a while to settle down, even if you make your service to run
after ntp, it still might correct time minutes or sometimes hours later.
Im pretty sure that what your service is doing is totally wrong and you
might want to fill a bug report to whoever wrote it and point them to
inotify(7)
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
