Re: [systemd-devel] systemd - how to run system service by user target

On Thu, 20.10.16 05:23, Kamil Jońca (kjo...@o2.pl) wrote: > Lennart Poettering writes: > > > On Wed, 19.10.16 12:46, Kamil Jońca (kjo...@o2.pl) wrote: > > > >> > >> Assume we have openvpn.service. > >> This service neccessary only when I want to connect to my work from

Re: [systemd-devel] systemd - how to run system service by user target

Lennart Poettering writes: [...] > > Well, this would require a privilege elevation. You can configure that > by invoking "systemctl start --system" on the right system units, and > then telling PK via its policy language that your user shall be > allowed to do that. But

Re: [systemd-devel] How to deploy systemd-nspawn containers and use for deployment

On Thu, 20.10.16 12:35, Juanjo Presa (juan...@gmail.com) wrote: > I am comfortable with machinectl nowadays but maybe I miss some kind of > versioning of images generated. Do you have any advice or recommendation > about this? Versioning is hard. We have no concept for that in nspawn/machined,

Re: [systemd-devel] getting systemd 232 ready

On Thu, 20.10.16 04:00, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > Hi, > > I was hoping systemd 232 would be released before systemd.conf as a > nice simple release. Unfortunately before the conference started, there > were too many regressions and bugs open. Since then people have

Re: [systemd-devel] How to deploy systemd-nspawn containers and use for deployment

I am comfortable with machinectl nowadays but maybe I miss some kind of versioning of images generated. Do you have any advice or recommendation about this? On Thu, Oct 20, 2016 at 2:41 AM, Nathan Williams wrote: > Fwiw, if you're using Chef, the impending release of v3