Systemd-sysv-generator lacking native file

Ask Fedora Ask in English
1

I don’t know what systemd is can anyone help me solve this problem along with description of what error actually is…?

[    4.764018] EDAC amd64: Node 0: DRAM ECC disabled.
[    4.767388] systemd-sysv-generator[1062]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    4.767416] systemd-sysv-generator[1062]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    4.771792] zram_generator::generator[1064]: Creating dev-zram0.swap for /dev/zram0 (4096MB)

and this as well I don’t know what this is…

[    3.109161] systemd[1]: /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-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    3.128105] systemd[1]: /usr/lib/systemd/system/alsa-restore.service:15: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
[    3.139960] systemd[1]: /usr/lib/systemd/system/mcelog.service:8: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
2

All of these are warnings for the packagers of the software in Fedora Linux. They aren’t really meant for end users to worry about. None of them are serious, but they probably should be changed eventually. (Remember, much of what we do in Fedora is volunteer community effort, and so sometimes it takes a while for diagnostic messages like this to get to a level of priority that they get fixed.)

If you would like to be helpful, you could file bugs for each of these in the corresponding component in the “Fedora” product in https://bugzilla.redhat.com. That won’t result in an immediate fix but will bring it to the attention of the right people.

4 Likes
3

5 posts were split to a new topic: How do I format long lines of terminal text properly for this site?

8

There’s a bug report with a comment that explains the origin of the two files in /etc/rc.d/ that are the root cause of this. Years go by without anything being done about it.

https://bugzilla.redhat.com/show_bug.cgi?id=1698119

9

The file /etc/rc.d/init.d/README says this

Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initialization.
10

There are a lot of things to do! If this is something of particular interest to you, maybe you could help!