I got the following message while activating the systemd timer I’ve created:
sudo systemctl enable ascio_invoices.service
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
NEXT LEFT LAST PASSED UNIT ACTIVATES
Fri 2023-12-01 16:20:00 CET 2min 51s Fri 2023-12-01 16:15:15 CET 1min 52s ago ascio_invoices.timer ascio_invoices.service
I don’t see, why this notification (I’ve posted at the beginning) was thrown, as I do have an [Install]-Section in my .timer-File.
as this has the benefit, not only to work after next reboot, but also start the timer now.
But can you tell me… if the only difference of using parameter -now is the fact, that the timer immediately start… why do I got an error for the command without now?
I don’t see the logic behind… especially as the service-file is exactly the same, and contain an [Install]-Section.
If you’re going to use a systemd timer for something to do with your user account, then you should not start it with sudo, but rather as a --user service or timer. See…