ostree/src
Colin Walters 2c326d705e fetcher: Log failures into journal
Particularly when HTTP requests fail, I really want a lot more information.
We could theoretically stuff it into the `GError` message field, but
that gets ugly *fast*.

Using the systemd journal allows us to log things in a structured fashion.
Right now e.g. rpm-ostree won't be aware of this additional information,
but I think we could teach it to be down the line.

In the short term, users can learn to find it from `systemctl status rpm-ostreed`
or `journalctl -b -r -u rpm-ostreed`, etc.

One thing I'd like to do next is log successful fetches of e.g. commit objects
as well with more information about the originating server (things like the
final URL if we were redirected, did we use TLS pinning, what was the negotiated
TLS version+cipher, etc).

Closes: #708
Approved by: jlebon
2017-02-24 22:30:24 +00:00
..
boot boot: Ensure we remount /var writable before systemd does journal flush 2016-09-15 19:41:44 +00:00
libostree fetcher: Log failures into journal 2017-02-24 22:30:24 +00:00
libotutil lib: Ensure an error is set in ensure_unlinked() if errno != ENOENT 2017-02-20 14:36:09 +00:00
ostree tree-wide: Squash noncritical compiler warnings 2017-02-24 17:08:27 +00:00
rofiles-fuse rofiles-fuse: Support write/read_buf() 2017-02-14 14:59:28 +00:00
switchroot ostree-prepare-root: Fix running with musl 2016-09-01 20:17:58 +00:00