On Sat, 25.01.14 16:41, Dominique Michel (dominique.mic...@vtxnet.ch) wrote:
> > So there is a 5s timeout before displaying that, but all it does is > > tell you how many jobs are waiting and not how long it's going to > > wait for them. > > > > If the user sits and watches that animation for 20s they'll likely > > think "ahh well this is stuck" and yank the cord, not knowing that > > things will be done cleanly if they just wait another 10s. > I fully agree. At my work, 20s are already a lot of time when it is > time to go. > > > > > If we displayed a timeout clock here too, users would be more willing > > to wait. > It would also be nice to show which process systemd is waiting for, > together with something like > Press Ctrl+C to abort and continue > > Most important is the possibility to abort the wait and continue, > because I am sure some peoples I know will just think "What is this > f. s." and yank the cord anyway. I like the theory of this, but I am not sure how to implement this nicely, since it is usually not clear what precisely the unit is that isn't showing up... Also, it's security sensitive I think, so it cannot be enabled by default I think... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
