OK , I think I found the reason.
I get the IP via DHCP, which also brings in the DNS servers (the two
secondaries). This somehow gets used by resolved, as it puts the resolvers
in /run/systemd/resolve/resolv.conf.
Since /etc/hosts is linked to /run/systemd/resolve/stub-resolv.conf which
just poin
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
/etc/syst
Well, it does wait when I press the power button on the case.
It does not wait if I enter as root poweroff or reboot.
I assume the first one goes through the logind while the second case does straight to systemd...
Regards,
Ralf
Gesendet: Dienstag, 04. September 2018 um 18:40 Uhr
Von: "
2018-09-04 18:17 GMT+02:00 Ralf Sieger :
> Hi Michael,
>
> this solution has a couple of drawbacks:
> - block will let shutdown, etc. fail, I do only need a pause/wait
> - delay does not work with reboot
It should work for shutdown, i.e. reboot.
--
Why is it that all of the instruments seeking
Hi Michael,
this solution has a couple of drawbacks:
- block will let shutdown, etc. fail, I do only need a pause/wait
- delay does not work with reboot
Regards,
Ralf
Gesendet: Sonntag, 02. September 2018 um 19:15 Uhr
Von: "Michael Biebl"
An: "Ralf Sieger"
Cc: "systemd Mailing
Am Mo, 3. Sep 2018, um 16:47, schrieb Mantas Mikulėnas:
> On Mon, Sep 3, 2018 at 3:41 PM Manuel Wagesreither
> wrote:>> Hallo all!
>>
>> I'm working on an embedded project consisting of an host and
>> numerous virtual machines and am facing problems related to time
>> management. systemd-times
