Bug 1925914
| Summary: | livesys and livesys-late | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | George Petasis <petasisg> |
| Component: | initscripts | Assignee: | Lukáš Nykrýn <lnykryn> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | deekej, forummail, jamacku, jonathan, kdudka, kzak, laurent.rineau__fedora, lnykryn, tjamadeira, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-06-08 15:17:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
George Petasis
2021-02-07 10:55:10 UTC
I deleted the scripts and can boot on Drippy my Fedora test server. I'm using Fedora 34 to write this message and it appears fine. Ripping it out was the bloodiest and quickest option available to me. As best I can tell the scripts don't do anything after install except make systemd squall. In rare cases scripts there conflict with systemd and it will happily crash your server. But it can do that with it's own scripts. Thanks for the pointer to the other files. It's been a while since I touched anything sysv. They're just links and I've eradicated them. I'm about to check that this boots Drippy my Fedora test server is booting just fine without all that kerfuffle. On another forum systemd is squalling according to the creator of it 'to get people to stop using sysv'. I'm paraphrasing that and removing some unfortunate wording. I did not bother to seek a better reason for that squalling. The mechanism to replace simple sysv type scripts is a systemd mechanism. This is documented here and probably other places but this was easier for me to understand. https://www.howtogeek.com/687970/how-to-run-a-linux-program-at-startup-with-systemd/ Now I recall that I used this convoluted mechanism to duplicate my personal reboot log independent of system logging which worked perfectly with sysv and systemd's sysv mechanism up until this squalling started. The script was when I learned sysv initscripts a couple decades ago and which I recently moved to systemd to shut up the squalling. I no longer maintain systems, just report what bugs I can where I can. @ (In reply to James Caldwell from comment #2) > Drippy my Fedora test server is booting just fine without all that > kerfuffle. On another forum systemd is squalling according to the creator of > it 'to get people to stop using sysv'. I'm paraphrasing that and removing > some unfortunate wording. I did not bother to seek a better reason for that > squalling. > > The mechanism to replace simple sysv type scripts is a systemd mechanism. > This is documented here and probably other places but this was easier for me > to understand. > > https://www.howtogeek.com/687970/how-to-run-a-linux-program-at-startup-with- > systemd/ > > Now I recall that I used this convoluted mechanism to duplicate my personal > reboot log independent of system logging which worked perfectly with sysv > and systemd's sysv mechanism up until this squalling started. The script was > when I learned sysv initscripts a couple decades ago and which I recently > moved to systemd to shut up the squalling. I no longer maintain systems, > just report what bugs I can where I can. I am not sure what is expected from me. The only way this will get fixed is by removing those scripts. Let's just pray that this happens at some point. *** This bug has been marked as a duplicate of bug 1698119 *** |