A Linux administrator is scheduling a system job that runs a script to check available disk space every hour. The Linux administrator does not want users to be able to start the job. Given the…

Question

Options

• AThe checkdiskspace.timer unit should be enabled via systemctl.
• BThe timers.target should be reloaded to get the new configuration.
• CThe checkdiskspace.timer should be configured to allow manual starts.
• DThe checkdiskspace.timer should be started using the sudo command.

• A
  15% (5)
• B
  6% (2)
• C
  55% (18)
• D
  24% (8)

Explanation

The most likely reason the timer will not start is that the checkdiskspace.timer should be configured to allow manual starts. By default, systemd timers do not allow manual activation via systemct1 start, unless they have RefuseManualStart=no in their [Unit] section. This option prevents users from accidentally starting timers that are meant to be controlled by other mechanisms, such as calendar events or dependencies. To enable manual starts for checkdiskspace.timer, the administrator should add RefuseManualStart=no to its [Unit] section and reload systemd.

No community discussion yet for this question.