Arch Linux

nmiculinic

Member

Registered: 2015-12-25

Posts: 63

Systemd --user mislogs service output

I have a user service in file /home/lpp/.config/systemd/user/gdisk.service.
Content of the file is as follows:

[Unit]
Description=Google-disk
Documentation=https://github.com/vitalif/grive2/

[Service]
Type=simple
ExecStart=/usr/bin/grive -p /home/lpp/gdrive

[Install]
Alias=default.target

When I start it, it executes normally and I see it's output on journal --user -f:

Apr 30 03:14:25 nmic-laptop systemd[929]: Starting Google-disk...
Apr 30 03:14:26 nmic-laptop grive[23514]: Reading local directories
Apr 30 03:14:26 nmic-laptop grive[23514]: Reading remote server file list
Apr 30 03:14:50 nmic-laptop grive[23514]: Synchronizing files
Apr 30 03:14:50 nmic-laptop grive[23514]: Finished!

However when I try seeing only journalctl --user -u gdrive I get no-entries list. Why?

P.S.
How do I make this service run after network connection is established?

Last edited by nmiculinic (2016-04-30 02:20:58)

WorMzy

Forum Moderator

From: Scotland

Registered: 2010-06-16

Posts: 11,845

Website

Re: Systemd --user mislogs service output

Mod note: Not a System Administration topic, moving to NC.

when I try seeing only journalctl --user -u gdrive I get no-entries list. Why?

Because the service is called grive, not gdrive?

P.S.
How do I make this service run after network connection is established?

Read up on Wants= and After= in 'man systemd.unit'.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

nmiculinic

Member

Registered: 2015-12-25

Posts: 63

Re: Systemd --user mislogs service output

Mod note: Not a System Administration topic, moving to NC.

when I try seeing only journalctl --user -u gdrive I get no-entries list. Why?

Because the service is called grive, not gdrive?

P.S.
How do I make this service run after network connection is established?

Read up on Wants= and After= in 'man systemd.unit'.

Thank you for reply. I found the solution. This doesn't work:

journalctl --user --unit=gdisk.service

while this does:

journalctl --user-unit=gdisk.service

I cannot really understand from documentation why the former doesn't work though.