If you're on a distribution running recent version of software, note
that prefix delegation is completely dysfunctional as of 251 [1].
[1] https://github.com/systemd/systemd/issues/23546
> use DNSStubListenerExtra=
It's indeed this directive I'm using on the downstream interface. Maybe
I should have mentioned that.
Configuration / results (MACs etc. obfuscated, but all correct on the
running system):
# head -n-0 /etc/systemd/network/linux-dummy_local0.{netdev,network}
==>
Hi, Petr.
> Do you need any systemd-resolved specific features?
Primarily, it's about the way directive Domains allows for directing
queries to particular DNS servers based on the queries' domains.
I'm using it to restrict the ISP's DNS server to the ISP's domain, use a
local DNS server for
to labels in /dev/disk/by-label so far.
On a side note several partitions tagged by the same partition label
will probably exist on nearly every system. As /dev/disk/by-partlabel
seems to reference only one per label I wonder whether this directory
makes any sense at all.
Regards,
Peter
,
see section Description) systemd-gpt-auto-generator is supposed to
behave like this by now already.
So maybe a bug in systemd-gpt-auto-generator manifesting only in the
context of BIOS + GPT?
Regards,
Peter Mattern
___
systemd-devel mailing list
Similar findings can result from running systemd ≥ 209 on a kernel
compiled without CONFIG_FHANDLE.
You may want to check this on your system.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
man machine-info lacks hostnamed chassis type embedded as introduced in 218.
The following lines should fix this.
---
man/machine-info.xml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/man/machine-info.xml b/man/machine-info.xml
index c654daa..9bf2bcb 100644
---
Thanks for fixing this.
May I suggest to adjust man systemctl accordingly, too?
Necessary parts would be the one about option --reverse and command
list-dependencies.
As for the latter I'd suggest another change while you're at it. Phrase
required and wanted units is rather ambiguous as it
Hello.
Right now systemctl's command list-dependencies is considering
parameters Wants and Requires only.
But given that command's purpose I was wondering whether it wouldn't
make sense to have it consider BindsTo as well.
Regards,
Peter Mattern
Separating the unit to sync time from the ones featuring OnCalendar by
time-sync.target (or any arbitrary target used as separating wall)
worked exactly as expected on ARM and is indeed a workaround for the
problem.
Couldn't reproduce the need to set DefaultDependencies=No in the units
If one of these options gets stated more than once the different
instances seem to be linked by a logical AND, too. This prevents
overwriting these options via snippets in /etc, e. g.
systemd-timesyncd.service still won't run in KVM with a snippet
First, thank you very much for your quick responses.
I had missed the description in man systemd.unit (If any of these
options is assigned the empty string, ... at the end of the paragraph
about Condition*, right?) and a snippet as posted by Michal works (I had
already checked this myself but
implementation.
I don't know whether something could or should be done about this
(personally I think yes), but thought it might make some sense to report
here.
Regards,
Peter Mattern
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http
13 matches
Mail list logo
