Control: tag -1 - moreinfo + confirmed Hi Jörg.
Jörg Sommer wrote: > > So I assume that -- if we include your file -- > > /etc/X11/Xsession.d/90unclutter will need to check if its running > > under systemd and if it discovers that it is running under systemd, > > then do nothing? (BTW: What's the best way to do such a check?) > > The best way should be checking for the $MANAGERPID (see systemd.exec(5)). > To support non-systemd systems it would be necessary to have the > 90unclutter script. > > If there's such a check in 90unclutter, it is possible to install the > unit as disabled and run `systemctl --user start unclutter` when systemd > is available. Thanks for these hints. Will check for the next upload. (A new version of the unclutter package currently waits in the NEW queue.) > > > and it aggregates all log messages via journal. > > > > So far that's the only advantage I see of that .service file. > > Another advantage would the possibility to restart unclutter after updates > of system libraries. If it aligns this way, *needrestart* shows the > unclutter unit, when it needs to be restarted after updates. Is needrestart (or needrestart-session) in the meanwhile able to restart such user services? IIRC needrestart-session could just inform the user about necessary restarts in a pop up notification. > The systemd unit also provides the easy enforcement of some security > constraints. I didn't check it, but `NoNewPrivileges=true` and > `ProtectHome=read-only` might be working. Good point. Both suggestions look fitting on a first glance. Will check. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE