On Mi, 25.10.17 04:52, 林自均 (johnl...@gmail.com) wrote:
> Hi Lennart,
>
> Yes, it makes sense to me. Thank you for your explanation.
>
> However, I still have a question about it. If the general goal is to
> minimize synchronization points, why don't we convert more active targets
> into passive
Hi Lennart,
Yes, it makes sense to me. Thank you for your explanation.
However, I still have a question about it. If the general goal is to
minimize synchronization points, why don't we convert more active targets
into passive targets? For example: not all machines have swap, so can the
On Do, 19.10.17 09:46, 林自均 (johnl...@gmail.com) wrote:
> Hi Andrei,
>
> Thank you for your reply!
> Just to confirm: there are about 10 passive system targets in
> systemd.special(5):
>
> - getty-pre.target
> - cryptsetup-pre.target
> - local-fs-pre.target
> - network.target
> -
On Mo, 16.10.17 15:15, 林自均 (johnl...@gmail.com) wrote:
> Hi folks,
>
> I am reading systemd documents, and I find passive target units a little
> bit confusing.
>
> Take "network.target" for example:
>
> "systemd-networkd.service" specifies "Wants=network.target" and
> "Before=network.target".
Hi Andrei,
Thank you for your reply!
Just to confirm: there are about 10 passive system targets in
systemd.special(5):
- getty-pre.target
- cryptsetup-pre.target
- local-fs-pre.target
- network.target
- network-pre.target
- nss-lookup.target
- nss-user-lookup.target
- remote-fs-pre.target
-
16.10.2017 18:15, 林自均 пишет:
> Hi folks,
>
> I am reading systemd documents, and I find passive target units a little
> bit confusing.
>
> Take "network.target" for example:
>
> "systemd-networkd.service" specifies "Wants=network.target" and
> "Before=network.target". That effectively makes
Hi folks,
I am reading systemd documents, and I find passive target units a little
bit confusing.
Take "network.target" for example:
"systemd-networkd.service" specifies "Wants=network.target" and
"Before=network.target". That effectively makes starting
"systemd-networkd.service" brings up both
