On 11 January 2015 at 18:08, Dimitri John Ledkov <[email protected]> wrote: > At the moment JobNew and JobRemoved signals are not useful for > tracking streams of events. JobType is missing from both of them, and > thus one can only track that "something" is happening and to which > units (And whether "something" is about to happen, finished, failed, > got aborted etc.). To get the JobType, one needs to query property > from the job, however this works only for "slow" jobs, typically the > job is gone on the systemd side already and thus subscriber has no > chance in quering the job type.
Whilst I still believe this is a valid bug in this signal, there is no urgency in resolving this. In my particular use-case that I wanted to use it for, I think I can use an alternative solution involving generators / templated instance targets. -- Regards, Dimitri. Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
