[systemd-devel] How to allow a user to use journalctl to see user-specific systemd service logs?

I am running user-level services in Ubuntu 16.04 LTS. For example, I have my test.service located at ~/.config/systemd/user/test.service I was able to run the service by doing systemctl --user start test.target However, when I try to read its log using journalctl, I got this error

Re: [systemd-devel] How to allow a user to use journalctl to see user-specific systemd service logs?

On 03.10.2016 20:59, Daniel Ng wrote: > I am running user-level services in Ubuntu 16.04 LTS. For example, I have > my test.service located at ~/.config/systemd/user/test.service > > I was able to run the service by doing > > systemctl --user start test.target > Hi Daniel, did you really

Re: [systemd-devel] How to allow a user to use journalctl to see user-specific systemd service logs?

On Mon, Oct 3, 2016 at 9:59 PM, Daniel Ng wrote: > I am running user-level services in Ubuntu 16.04 LTS. For example, I have > my test.service located at ~/.config/systemd/user/test.service > > I was able to run the service by doing > > systemctl --user start

Re: [systemd-devel] How to allow a user to use journalctl to see user-specific systemd service logs?

I actually meant to say "systemctl --user start test.*service*" In Ubuntu 16.04 system with systemd 229, I was able to bypass the permission error by adding the user to group "adm", but now the user can see the journal of system units as well. One weird thing now is that "journalctl --user-unit

Re: [systemd-devel] How to allow a user to use journalctl to see user-specific systemd service logs?

On 03.10.2016 20:59, Daniel Ng wrote: > journalctl --user -u test.service > Hint: You are currently not seeing messages from other users and the > system. > Users in the 'systemd-journal' group can see all messages. Pass -q to > turn off this notice. > No journal files