It would be cool to have a flag file by which systemd could be informed whether plymouth is running or not. Harald has for now implemented a scheme like this in dracut: When plymouth is started from initrd (and only then) the following additional shell fragment is executed: mkdir -m 755 -p /dev/.systemd || : touch /dev/.systemd/plymouth || : systemd when finding that flag file will do two things: a) enable status outputs (i.e. "Starting Apache ...") to /dev/console even though "quiet" is passed on the kernel command line b) refrain from starting Plymouth again, after boot. (which we do to support initrd-less boots) it would be cool if equivalents to the shell script showed above could be added to native C code in Plymouth. As soon as that happens we could then drop these commands from dracut to speed things up a little (two processes less). If these commands fail for some reason this should be ignored. If you prefer to use a flag file like /dev/.plymouth/started this would be OK too.
Please use /run/plymouth/started instead of the path mentioned above.
Created attachment 488611 [details] a patch that creates and removes the flag file Here's a patch that creates this flag file (Not much tested). This will create /run/initramfs/plymouth on plymouth startup and remove the file on shutdown. systemd can use that to control the status output and to start plymouth if it wasn't started yet by the initrd. If this is in place and with current systemd git then 6e748588cddeea5b96a350f97e415fbab4994ae2 can be dropped. I'd like to ask you to do that, to avoid two-way communication between systemd and plymouth. I think systemd should pass data to plymouth, and not the other way round.
We now use Plymouth' PID file for this, so I figure this can be closed.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.