Bug 1889923 - Standard output type syslog is obsolete
Summary: Standard output type syslog is obsolete
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 33
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-20 23:24 UTC by nacho_trebuchet
Modified: 2020-10-21 06:43 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
systemd-analyze_output (3.94 KB, application/octet-stream)
2020-10-20 23:24 UTC, nacho_trebuchet
no flags Details

Description nacho_trebuchet 2020-10-20 23:24:01 UTC
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

Comment 1 Zbigniew Jędrzejewski-Szmek 2020-10-21 06:43:59 UTC
Yep, we're trying to stop the use of this mode (as explained in the message). This has nothing to do with your
unit. systemd-analyze simply always prints all errors for all units.


Note You need to log in before you can comment on or make changes to this bug.