On 12/05/2013 10:08 AM, Mantas Mikulėnas wrote:
> One of the problems mentioned is that services can be started only
when they are used for the first time. As I understood it, you can make
sure that a service is always loaded, so that there is no waiting time
the first time it is called.
This is not a problem. This is a configuration choice. If the service
supports activation, you *can* let it be activated if that suits you,
but you can also configure it to be started on boot as any other service
(i.e. make multi-user.target depend on the service directly).
OK, when I use:
[Install]
WantedBy=multi-user.target
What I did until now, the service is just started.
When I do not use it, only a socket is made and it is started the first
time it is used.
Correct?
When a service is started because it was used (loaded on the first use),
does it keeps running, or is it unloaded after some time? Or can this be
configured?
> I understood you could deny a service network connection. How is this
done? Until no I could not find it. Is it possible to limit the
bandwidth a service is allowed to use?
PrivateNetwork=yes will create a dedicated net namespace for that
service, which does not have any network interfaces by default.
(Relevant man pages: clone, unshare, setns, nsenter; LXC also uses this.)
OK, it is an on/off switch. There is not a possibility to limit the
bandwidth?
Met vriendelijke groet,
Cecil Westerhof
Engineer
mobiel +31 - 6 - 25 00 38 81
--
Snow B.V.
Unix Specialists
De Ooyen 11
4191 PB Geldermalsen
http://www.snow.nl
tel. +31 - 345 - 65 66 66
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
