Allison Karlitskaya

Thanks for the report/question. This doesn't exist yet, but I plan to add UI for it. I'm on vacation right now and won't be back until mid August, though.

``` read(8, "invalid or unusable locale: en_CA.UTF-8\n736\n0:1\n{\"status\":200,\"reason\":\"OK\",\"headers\":{\"Referrer-Policy\":\"no-referrer\",\"X-Frame-Options\":\"sameorigin\",\"Content-Security-Policy\":\"default-src 'self' http://127.0.0.2:9091; connect-src 'self' http://127.0.0.2:9091 ws://127.0.0.2:9091; form-action 'self' http://127.0.0.2:9091; base-uri 'self' http://127.0.0.2:9091; object-src 'none'; font-src 'self' http://127.0.0.2:9091 data:; img-src 'self' http://127.0.0.2:9091 data:; block-all-mixed-content\",\"Cross-Origin-Resource-Policy\":\"same-origin\",\"X-Cockpit-Pkg-Checksum\":\"9ccf9e4178b7ca0494b34c4e3acb35807a078b0e74493066ca41843da73200e0\",\"X-DNS-Prefetch-Control\":\"off\",\"X-Content-Type-Options\":\"nosniff\",\"Content-Type\":\"text/html\",\"Access-Control-Allow-Origin\":\"http://127.0.0.2:9091\"}}",...

One small test script later, and yes. Despite the documentation saying: > Note that the daemon software configured for socket activation with socket units needs to be able to accept...

I did the `StandardError=journal` thing, as suggested by @martinpitt. Kinda frustrating that this isn't the default behaviour, but it seems to be working now, thanks!

> > Why not just use `git blame -w`? (and `-C -M` for that matter)? > Maybe we should discuss it in our weekly meeting :) :+1:

I think I'm really the wrong person for reviewing this PR, although I can think of one scenario where it might be useful which doesn't violate any assumptions about the...

Can you please be more specific about what the problem is here? Is that something in the journal? Are you able to connect anyway?

Okay, but what's the problem? Are you unable to connect? Are you able to connect? Is this just noise in the journal that's bothering you?

Fix is on the way in cockpit-project/bots#3734

PR'd in #17321.