Re: [systemd-devel] Showing plymouth shutdown splash earlier during shutdown process
On Fri, Jun 1, 2012 at 4:03 AM, Michal Schmidt mschm...@redhat.com wrote: On 05/31/2012 05:46 PM, Daniel Drake wrote: In the case of reboot (or poweroff), what does this mean? plymouth-reboot.service is queued to start, and prefdm.service is queued to stop. What does After= mean in this context, who comes first? 'man systemd.unit' says: If one unit with an ordering dependency on another unit is shut down while the latter is started up, the shut down is ordered before the start-up regardless whether the ordering dependency is actually of type After= or Before=. Thanks for pointing that out. It is like it is waiting for those services to stop before executing. How can I find out why? Based on the above rule, check all the ordering dependencies the unit has: systemctl show -p After -p Before plymouth-reboot.service I followed this down a couple of levels and didn't find the answer. Probably need to go further, I'll see if I can find some time to do that soon. Thanks Daniel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Showing plymouth shutdown splash earlier during shutdown process
On 05/31/2012 05:46 PM, Daniel Drake wrote: In the case of reboot (or poweroff), what does this mean? plymouth-reboot.service is queued to start, and prefdm.service is queued to stop. What does After= mean in this context, who comes first? 'man systemd.unit' says: If one unit with an ordering dependency on another unit is shut down while the latter is started up, the shut down is ordered before the start-up regardless whether the ordering dependency is actually of type After= or Before=. It is like it is waiting for those services to stop before executing. How can I find out why? Based on the above rule, check all the ordering dependencies the unit has: systemctl show -p After -p Before plymouth-reboot.service Michal ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Showing plymouth shutdown splash earlier during shutdown process
On Wed, Apr 11, 2012 at 10:51 AM, Daniel Drake d...@laptop.org wrote: On Wed, Apr 11, 2012 at 9:42 AM, Lennart Poettering lenn...@poettering.net wrote: I tried modifying e.g. plymouth-reboot.service to have: Before=reboot.service shutdown.target umount.target final.target reboot.target That suggests that the plymouth client tool is not waiting for the operation to finish but just asynchonrously queueing the reuest, which is something that should be fixed in plymouth. You're probably right, but before we get there, even with the above Before= change, systemd seems to be starting plymouth-reboot.service rather late in the process. Logs from a reboot with the Before= change made as above: http://dev.laptop.org/~dsd/20120411/shutdown2.txt Any ideas? Bump. I filed a bug for the plymouth-quitting-before-command-processed issue: https://bugs.freedesktop.org/show_bug.cgi?id=50544 and I worked around it locally. But still, the plymouth splash is being shown late in the process, as shown in the above log. plymouth-reboot.service has After=getty@tty1.service prefdm.service plymouth-start.service Before=reboot.service In the case of reboot (or poweroff), what does this mean? plymouth-reboot.service is queued to start, and prefdm.service is queued to stop. What does After= mean in this context, who comes first? Either way, plymouth-reboot.service seems to be run a long time after prefdm finishes - about 3.5 seconds. And after running it a few times I am seeing that it *always* starts after a whole bunch of other services have been stopped - in the above log: diskspacerecover.service, alsa-store.service, systemd-random-seed-save.service, and maybe more. It is like it is waiting for those services to stop before executing. How can I find out why? Thanks Daniel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Showing plymouth shutdown splash earlier during shutdown process
Hi, As can be seen in my logs of a reboot: http://dev.laptop.org/~dsd/20120411/shutdown.txt The plymouth shutdown splash is being shown really quite late. As systemd shuts down fantastically fast, this means that our pretty shutdown graphic is not being drawn on OLPC laptops. Sometimes the image is drawn partially, and sometimes it is not drawn at all. (A few seconds of systemd output text is always visible though) Is there a way to make the plymouth shutdown screen appear earlier? I tried modifying e.g. plymouth-reboot.service to have: Before=reboot.service shutdown.target umount.target final.target reboot.target However this didn't produce any noticable difference. Thanks, Daniel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Showing plymouth shutdown splash earlier during shutdown process
On Wed, 11.04.12 09:25, Daniel Drake (d...@laptop.org) wrote: Hi, As can be seen in my logs of a reboot: http://dev.laptop.org/~dsd/20120411/shutdown.txt The plymouth shutdown splash is being shown really quite late. As systemd shuts down fantastically fast, this means that our pretty shutdown graphic is not being drawn on OLPC laptops. Sometimes the image is drawn partially, and sometimes it is not drawn at all. (A few seconds of systemd output text is always visible though) Is there a way to make the plymouth shutdown screen appear earlier? I tried modifying e.g. plymouth-reboot.service to have: Before=reboot.service shutdown.target umount.target final.target reboot.target That suggests that the plymouth client tool is not waiting for the operation to finish but just asynchonrously queueing the reuest, which is something that should be fixed in plymouth. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Showing plymouth shutdown splash earlier during shutdown process
On Wed, Apr 11, 2012 at 9:42 AM, Lennart Poettering lenn...@poettering.net wrote: I tried modifying e.g. plymouth-reboot.service to have: Before=reboot.service shutdown.target umount.target final.target reboot.target That suggests that the plymouth client tool is not waiting for the operation to finish but just asynchonrously queueing the reuest, which is something that should be fixed in plymouth. You're probably right, but before we get there, even with the above Before= change, systemd seems to be starting plymouth-reboot.service rather late in the process. Logs from a reboot with the Before= change made as above: http://dev.laptop.org/~dsd/20120411/shutdown2.txt Any ideas? Thanks Daniel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
