> -----Original Message----- > From: systemd-devel-bounces+mhoyer=de.adit-jv....@lists.freedesktop.org > [mailto:systemd-devel-bounces+mhoyer=de.adit-jv....@lists.freedesktop.org] On > Behalf Of Umut Tezduyar > Sent: Thursday, July 18, 2013 8:38 PM > To: Lennart Poettering > Cc: Mailing-List systemd > Subject: Re: [systemd-devel] Has systemd booted up command > > On Thu, Jul 18, 2013 at 7:06 PM, Lennart Poettering <lenn...@poettering.net> > wrote: > > On Thu, 18.07.13 10:08, Umut Tezduyar (u...@tezduyar.com) wrote: > > > >> Hi, > >> > >> This is in reference to > >> https://bugs.freedesktop.org/show_bug.cgi?id=66926 request. > >> > >> I have been polling systemd with "systemctl is-active default.target" > >> to detect if boot up has been completed or not. I have noticed that > >> this is not enough though. > >> > >> It seems like starting a service that is not part of the initial job > >> tree can keep in state activating after default.target is reached. I > >> could use systemctl list-jobs to detect if there are still jobs > >> available but systemctl list-jobs's output is not meant for > >> programming. > >> > >> Same problem happens when I switch targets. Currently I rely on > >> systemctl list-jobs output to detect if the target switch has been > >> completed or not. > >> > >> What can we do about it?
Why not simply writing a unit notify_default_target_done.service that - is linked into multi-user.target.wants - and defines: After=default.target Should work to my understanding ... Cheers, Marko _______________________________________________ systemd-devel mailing list firstname.lastname@example.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel