Shijiang Wei b1594c59f5 use pubsub instead of filenotify to follow json logs ... inotify event is trigged immediately there's data written to disk. But at the time that the inotify event is received, the json line might not fully saved to disk. If the json decoder tries to decode in such case, an io.UnexpectedEOF will be trigged. We used to retry for several times to mitigate the io.UnexpectedEOF error. But there are still flaky tests caused by the partial log entries. The daemon knows exactly when there are new log entries emitted. We can use the pubsub package to notify all the log readers instead of inotify. Signed-off-by: Shijiang Wei <mountkin@gmail.com> try to fix broken test. will squash once tests pass Signed-off-by: Shijiang Wei <mountkin@gmail.com>		2016-02-15 19:25:16 +08:00
..
jsonfilelog.go	use pubsub instead of filenotify to follow json logs	2016-02-15 19:25:16 +08:00
jsonfilelog_test.go	add labels/env log option for jsonfile	2015-10-12 21:12:46 +02:00
read.go	use pubsub instead of filenotify to follow json logs	2016-02-15 19:25:16 +08:00