[18:46] <ParsectiX> Hi guys. I'm trying to use inotify API to monitor changes in a file. I'm monitoring for IN_IGNORED & IN_CLOSE_WRITE events. But I'm loosing the situation that I get when I monitor entire dir IN_MOVED_TO. IS there a way to catch all file changes monitoring only the file ?
[20:15] <lamont> bjf: re 1502238 - that's a server.... appport-collect ain't gonna provide happiness... what logs do you actually want?
[20:15] <lamont> ah, and it's an automated thing... can you peek at it and see what more info you might want?
[20:50] <bjf> lamont, if we need anything more we'll just request it on the bug .. i've set it to triaged so it should be fine now
[20:50] <bjf> jsalisbury, can you get LP: #1502238 that on our list
[20:50] <ubot5`> Launchpad bug 1502238 in linux (Ubuntu) "bridge does not forward neighbor solicitation packets" [Undecided,Triaged] https://launchpad.net/bugs/1502238
[20:53] <jsalisbury> bjf, ack
[20:54] <lamont> bjf: cool.  trivially reproducable with a firewall reboot
[20:57] <smoser> how reliable  is uptime?
[20:57] <smoser> from the perspective of reading uptime. and then reading again later and using it to tell the difference.
[20:58] <smoser> interested in that wrt the fact taht systemd-timesync might reset my clock in between my reads.