On Tue, 08.03.11 19:16, Andrey Borzenkov (arvidj...@mail.ru) wrote: > > On Mon, Mar 7, 2011 at 4:02 AM, Lennart Poettering > <lenn...@poettering.net> wrote: > > On Sat, 05.03.11 14:27, Andrey Borzenkov (arvidj...@mail.ru) wrote: > > > >> pts/1}% systemctl --no-pager show systemd-tmpfiles-clean.service > >> Id=systemd-tmpfiles-clean.service > >> Names=systemd-tmpfiles-clean.service > >> Wants=local-fs.target > >> Before=sysinit.target shutdown.target > >> After=systemd-tmpfiles-clean.timer systemd-readahead-collect.service > >> systemd-readahead-replay.service local-fs.target > >> Description=Cleanup of Temporary Directories > >> > >> So I know Before/After dependencies, but there is no way to find out > >> (without exhaustive search across all units) what may cause this unit > >> to be started. > >> > >> systemd already merges After/Before and displays final result; may be > >> it should do the same for WantedBy as well? > > > > Hmm? RequiredBy= and WantedBy= should be sufficient? No? > > > > Add in RequisiteBy and BoundBy and it makes it perfect :)
BoundBy exists, and the inverse of Requires and Requisite is both RequiredBy. > > (It will ignore stuff like units started by triggers.) > > > > TriggeredBy? :) Although I suspect it would require full unit search > in this case. Yeah, and for stuff like per-connection socket activation wouldn't really work anyway... Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
