Releases: coreos/locksmith
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Locksmith now writes an informational metadata file at the well known path
/run/update-engine/coordinator.conf
.
Other tools that fulfill a similar role may also safely write to that file by
ensuring an exclusive lock is held on it for the duration of them running.
v0.4.2
Locksmith now uses Restart=on-failure
in the systemd unit, so that if the reboot strategy is off, it is not constantly restart. Fixes coreos/bugs#1171.
v0.4.1
v0.4.0
Locksmith now uses github.com/coreos/etcd/client, instead of the deprecated
github.com/coreos/go-etcd.
Locksmith now uses github.com/coreos/pkg/capnslog for logging.
The reboot strategy best-effort
is deprecated, and locksmithd will complain
loudly if it is used. Please use an explicit reboot
or etcd-lock
strategy
instead.
Locksmith logs some information about the configured reboot window.
Locksmith supports etcd basic auth.
Locksmith again requires update-engine.service, and will start after
user-config.target system-config.target are reached.
v0.3.4
The environment variables controlling reboot windows (REBOOT_WINDOW_START
,
REBOOT_WINDOW_LENGTH
) have been renamed to include the prefix LOCKSMITHD_
to maintain consistency with other locksmithd environment variables.
The old environment variables are still read to maintain compatibility with
locksmithd v0.3.1 to v0.3.3.