On Tue, 3 Nov 2015, at 02:27 AM, Lennart Poettering wrote: > Hmm, maybe there's something wrong with the ACLs on the journal files > or the directory they reside in? Normally, there should be an ACL that > allows the "systemd-journal" group access to all files, and > systemd-journal-gatewayd is running with that group among its > auxiliary group ids...
Still at a loss to resolve this. How I loathe unix permissions. I'd rather run systemd-journal-gatewayd as my user instead systemd+ as it's running now to avoid this time wasting exercise. > CORS? I don't know what that means? It's a Web server header that permits what Web apps can interact with it. https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS So a possible API would be: /usr/lib/systemd/systemd-journal-gatewayd --header="Access-Control-Allow-Origin: *" Which would be seen in the output of `curl -I 'http://localhost:19531/entries?boot'`, and the * would allow any Web app no matter where it's hosted to get log events IIUC. So not a good default but could be useful. :) Cheers, _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
