Systemd-sysv-generator lacking native file

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.

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.

3 Likes

Hi @hhlp Can you tell me how did you make kind of sliding bars for this message that I had made…
Can you give me guide of how effectively I can create the topics that is highly comprehensible

Hello @superadmin you could consider to read through the resources provided in the #start-here category. Specifically the syntax conventions used by Discourse, the software used to run this forum.

1 Like

Sorry but I can’t find the Topic right now where we talked about how to reformating bash command and logs to guide this USER

Ohh my memory could you please can refresh my mind? :thinking::flushed:

Regards

I’ve found It

In this Topic i’ve explained Well how to reformat Well your topics…

Regards.,

3 Likes

This site uses a text-formatting system called “markdown”, similar to that used on Github, Stack Exchange, and a bunch of other places. See Markdown Reference for this. The “code formatting” part is particularly important for commands, because otherwise special characters can get messed up.

2 Likes