Nalin Dahyabhai ab62ecf393 Open the journald following descriptor earlier ... Following a journal log almost always requires a descriptor to be allocated. In cases where we're running out of descriptors, this means we might get stuck while attempting to start following the journal, at a point where it's too late to report it to the client and clean up easily. The journal reading context will cache the value once it's allocated, so here we move the check earlier, so that we can detect a problem when we can still report it cleanly. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>		2016-03-24 10:12:51 -04:00
..
journald.go
journald_unsupported.go
read.go	Open the journald following descriptor earlier	2016-03-24 10:12:51 -04:00
read_native.go	Try to handle changing names for journal packages	2016-02-23 12:24:27 -05:00
read_native_compat.go	Try to handle changing names for journal packages	2016-02-23 12:24:27 -05:00
read_unsupported.go