Created attachment 1723048 [details]
systemd-analyze_output

Description of problem: After creating rsync backup with systemd units, verification resulted in a list of warnings.


Version-Release number of selected component (if applicable): Fedora 33


How reproducible: Very 


Steps to Reproduce:
1. Create bash script
    $ sudo nano /opt/mybackup.sh
    $ sudo chmod +x /opt/mybackup.sh

2. Create service unit
    $ sudo nano /etc/systemd/system/mybackup.service

    # Service unit file

    [Unit]
    Description=Daily backup using rsync

    [Service]
    Type=simple
    ExecStart=/opt/mybackup.sh
    User=me

    $ sudo systemctl daemon-reload
    $ sudo systemctl start mybackup.service

 3. Create timer unit
    $ sudo nano /etc/systemd/system/mybackup.timer

    # Timer unit file

    [Unit]
    Description=Daily backup of home directory

    [Timer]
    Unit=mybackup.service
    OnBootSec=5min
    OnCalendar=daily
    Persistent=true

    [Install]
    WantedBy=timers.target

    $ sudo systemctl start mybackup.timer
    $ sudo systemctl enable mybackup.timer

4. Verify
    $ sudo systemd-analyze verify /etc/systemd/system/mybackup.*

5. Observe output (warnings) unrelated to newly created unit files
/usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control


Actual results: Received warnings unrelated to the unit files created for backups
Output:  /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control


Expected results:
Status verifies newly created service is loaded and active


Additional info:  The verification command produced a list of warnings, one with plymouth-start.service reported here, and a list of dracut warnings previously reported with Bug 1873286