4 Commits

Author	SHA1	Message	Date
Ruslan Usifov	b3c72d1729	close file handle when FileRotator object will closed. Fixes https://github.com/hashicorp/nomad/issues/6309 (#6323)	2019-09-13 10:31:13 -04:00
Michael Schurter	e37bc3513c	logmon: ensure errors are still handled properly ... ...and add a comment to switch back to the old error handling once we switch to Go 1.12.	2019-07-22 12:49:48 -07:00
Marcin Matlaszek	39eec70f31	Recover from any possible io error when invoking Write on FileRotator ... As of now, FileRotator uses bufio.Write under the hood to write data to configured output file. Due to the way how bufio handles any occurred io error - saves it into `err` variable never resetting it automatically - any operation like `Write`, `Flush` etc will become a no-op, returning the very same, saved error (eg. Out of disk space) even when the problem is fixed (eg. disk space is available again). That automatically means that FileRotator will stop writing any logs, reporting the same error over and over again, even if it's no longer valid. This PR fixes it by resetting the bufio Writer, which resets any errors and tries to write requested data.	2018-12-07 18:22:29 +01:00
Danielle Tomlinson	6b72e96eba	client: Move driver/logging to logmon/logging ... The logging package is used by logmon and the legacy mock_driver. Because the legacy drivers are going away, I'm moving it here to signify its actual ownership.	2018-11-30 10:46:13 +01:00

Renamed from client/driver/logging/rotator.go (Browse further)