主页 / unix / 问题 / 680669
Accepted
Boris Hamanov
Asked: 2021-12-09 06:34:21 +0800 CST

OnCalendar systemd 计时器单元仍在启动时执行，如何停止它？

  • 772

我启用并启动了以下单元

[Unit]
Description=Schedule a nightly execution at 03.15 for Backup ROOT
# Allow manual start
RefuseManualStart=no
# Allow manual stop
RefuseManualStop=no

[Timer]
#Execute job if it missed a run due to machine being off
Persistent=false
# Run every night 03.15
OnCalendar=*-*-* 03:15:00
#File describing job to execute
[email protected]

[Install]
WantedBy=timers.target

它会在每晚凌晨 3.15 点正确运行，但它也会在启动时运行，因为它会造成混乱！为什么会发生这种情况以及如何阻止它？

linux fedora

1 个回答

  1. Best Answer

    防止 systemd timer from running on startup的这个答案很好地回答了这个 问题。

    我会总结

    问题是我总是在 .service 文件的 [Install] 部分中包含类似 WantedBy=basic.target 的内容（因为它是标准 systemd 服务复制面食的一部分）。事实证明，这实际上会导致该单元在 basic.target 为（又名系统启动）时启动。

    https://www.freedesktop.org/software/systemd/man/systemd.unit.html#WantedBy= https://www.freedesktop.org/software/systemd/man/systemd.special.html#basic.target

    TLDR；您不希望 .timer 文件触发 .service 文件中的 [Install] 部分。

    作为附加步骤，您必须使用systemctl disable [service_name]禁用您的服务

    然后您会注意到，如果您想再次启用它，则无法启用，并且会显示类似的错误：

    注意说的部分

    ...在需要时通过激活（套接字、路径、计时器、...

    The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled 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/ or .requires/ 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.
    • 2

相关问题