On Wed, 2021-06-30 at 19:41 +0800, Ed Greshko wrote:
> > But of course there's always something else. After logging out, the
> > service is killed, which is fine, but it doesn't start again with a
> > new
> > login. I assumed that user units would do this automatically, but it
> > seems they don't.
>
> Maybe ignore my previous question.
>
> I've been playing with this as well. I found that with KDE I could get
> a service file to start at login by using
>
> After=plasma-core.target in the [Unit] section and
> WantedBy=plasma-core.target in the [Install] section
>
> I don't know if there is a general way to do it for all desktops.
Well I did that, but things are no better. The service still doesn't
restart after logging out and in again. In fact it's actually worse now
as it apparently doesn't start even the first time. I even did a clean
boot to check this and see:
$ systemctl --user status startinsync.service
○ startinsync.service - insync-headless service
Loaded: loaded (/home/poc/.config/systemd/user/startinsync.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Wed 2021-06-30 14:52:37 BST; 5min ago
Process: 3404 ExecStart=/bin/sh /usr/bin/insync-headless start (code=exited, status=0/SUCCESS)
Main PID: 4069 (code=exited, status=0/SUCCESS)
CPU: 2.813s
Jun 30 14:52:34 Bree systemd[3220]: Starting insync-headless service...
Jun 30 14:52:37 Bree systemd[3220]: Started insync-headless service.
Jun 30 14:52:37 Bree systemd[3220]: startinsync.service: Deactivated successfully.
Jun 30 14:52:37 Bree systemd[3220]: startinsync.service: Consumed 2.813s CPU time.
The current service file looks like this:
$ systemctl --user cat startinsync.service
# /home/poc/.config/systemd/user/startinsync.service
[Unit]
Description=insync-headless service
After=plasma-core.target
[Service]
Type=forking
ExecStart=/bin/sh /usr/bin/insync-headless start
[Install]
WantedBy=plasma-core.target
poc
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
