On Mon, 03.10.16 14:59, Daniel Ng (danieln...@gmail.com) 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
>
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
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
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
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