storj/pkg/process
Kaloyan Raev 958772467a cmd/storagenode-updater, pkg/process: Fix logging timestamp
After changing how we execute the storagenode-updater process we lost
timestamps in the log.

The fix is to start using zap logging.

The Windows Installer is changed to register the storagenode-updater
service in a way that the Windows Service Manager passes the
--log.output flag instead of the old --log.

The old --log flag is deprecated, but not removed. We will support it
for backward compatibility. This is required as the storagenode-updater
can auto-updated itself, but the Windows Service Manager of this old
installtion will continue passing the old --log flag when starting it.

Change-Id: I690dff27e01335e617aa314032ecbadc4ea8cbd5
Signed-off-by: Kaloyan Raev <kaloyan@storj.io>
2019-12-11 10:05:48 +00:00
..
config.go pkg/private/fpath: subsume AtomicWriteFile 2019-12-03 18:14:08 +00:00
debug.go private: rename internal to private (#3573) 2019-11-14 21:46:15 +02:00
error.go storagenode: more live request tracking (#2699) 2019-08-02 16:49:39 -06:00
exec_conf_test.go private: rename internal to private (#3573) 2019-11-14 21:46:15 +02:00
exec_conf.go cmd/storagenode-updater, pkg/process: Fix logging timestamp 2019-12-11 10:05:48 +00:00
exec.go private: rename internal to private (#3573) 2019-11-14 21:46:15 +02:00
logging.go cmd/storagenode-updater, pkg/process: Fix logging timestamp 2019-12-11 10:05:48 +00:00
metrics.go private: rename internal to private (#3573) 2019-11-14 21:46:15 +02:00
rand.go Initialize math/rand default source (#3552) 2019-11-12 10:03:41 -07:00