On Fri, 18 Mar 2011 14:11:47 +0300
Andrey Borzenkov <arvidj...@mail.ru> wrote:

> On Fri, Mar 18, 2011 at 8:31 AM, Mike Kazantsev <mk.frag...@gmail.com> wrote:
> >
> > That'd make all the systems with currently enabled services in
> > network.target.wants misconfigured - network should fail on these
> > unless something Requires= (or Wants=) network.target explicitly (which
> > was marked as a wrong way to depend on network), so I think maybe some
> > larger announcement for packagers is in order as well, to leave less
> > broken systems and angry users as a result ;)
> >
> 
> I am not sure I really understand this. When you speak about services
> WantedBy network.target - do you mean services activated on-demand
> when network becomes available.

No, these are services that make the network work.
They are pulled in for network.target, so any service starting after
that will be able to bind to some interface or connect to a remote host.


> Could you give example?

Sure, I have this mix (for two machines):

rpcbind.service
rpcidmapd.service
rpcstatd.service
wicd.service
ypbind-mt.service
epmd.service
ipsec.service
net@core.service
net-firewall.service
net@he6.service
net-lo.service
net@tnet.service
net@xtit.service

net@.service is just a template to start static network configuration
script, other net-* stuff follows the same purpose, the rest are more or
less what comes with the distro.
I'm fairly sure that common units for other stuff like connman,
wpa_supplicant or dhcpcd will also be in this category.


-- 
Mike Kazantsev // fraggod.net

Attachment: signature.asc
Description: PGP signature

_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to