Le mer. 29 août 2018 à 10:03, Michael Chapman a
écrit :
Thank you for the clarification.
> > Question 2: how can I configure the prog_two/prog_three case, i.e. having
> > them starting one after the other (= start prog_three when prog_two is
> > done), and have the prompt return immediately
>
Hello everyone
systemctl start myserv.service sometimes immediately returns to the shell
prompt and sometimes stays until the program is done. Specifically, taking
the example of two programs
- prog_one which starts in the foreground and never ends, defined as
ExecStart=/path/to/prog_one
-
Hello everyone,
v239 brought in portable services (a good description is at
http://0pointer.net/blog/walkthrough-for-portable-services.html) and while
I still cannot make it work (I do not have a /usr/lib/systemd/portablectl
despite having systemd --version reporting 239, but this is going to be
Le mer. 29 août 2018 à 17:11, Steve Dodd a écrit :
> On 29 August 2018 at 15:43, Steve Dodd wrote:
>
> Shouldn't be that hard to adapt one of the above for nspawn?
>
>
nspawn is not the problem - portable services are. I use a minimal image
with nspawn which is OK but portable services are
configurations (no DHCP), and probably as a way to overwrite DHCP provided
data.
Sorry for the noise.
Le mer. 5 sept. 2018 à 08:11, Wojtek Swiatek a écrit :
> Hello everyone,
>
> I decided to clean up my DNS resolving mess and fully go the
> systemd-resolved way = on every machi
Hello everyone,
I decided to clean up my DNS resolving mess and fully go the
systemd-resolved way = on every machine:
- have /etc/resolv.conf linked to /run/systemd/resolve/stub-resolv.conf
- have the resolver stub running on 127.0.0.53
- provide internal upstream and fallback servers in
Hello everyone
I would like to have a timer which runs every 60 seconds after the machine
is booted.
I thought that OnBootSec would be the right parameter but this is s a one
shot call - it starts 60 seconds after the boot and then the service is
done (does not restart ever)
Is there a way to
Le lun. 3 sept. 2018 à 17:30, Jérémy Rosen a écrit :
> You can put multiple criterion in a single .timer
>
> In your case, combining OnBootSec and OnUnitActiveSec should do what you
> want...
>
>
Thank you - that was it.
OnBootSec=60s
OnUnitActiveSec=60s
I did not realize that OnUnitActiveSec
Hello everyone,
I have an nspawn container which is currently connected to a bridge on the
host:
root@srv /e/s/nspawn# cat domotique.nspawn
[Exec]
Boot=yes
[Network]
Bridge=br0
#Bridge=wlx00c0ca384bd9
This results in a host0 interface being present in the container.
Everything works.
I now
