From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH] src: configure systemd-resolved's MulticastDNS= setting
Date: Thu, 11 Feb 2021 14:45:26 -0600 [thread overview]
Message-ID: <2ce451ab-0dd3-e386-391e-bc3afd8be9f8@gmail.com> (raw)
In-Reply-To: <1f997b5df5730f363e52fde58d08c50bade87899.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
Hi Daniel,
>> Is there a default? If so, it should be in bold. What happens if
>> this setting
>> is omitted?
>
> If the setting is omitted, we don't touch the default value. Which
Ok, so there's no default that iwd should pick.
> appears to be false, but somebody could patch systemd-resolved to
> change that, so I wasn't sure if that should be documented here. I'll
> add that though.
So instead we may want to mention that if this setting is omitted, the
systemd-networkd default is used.
>>> + mdns = l_settings_get_string(active_settings, "Network",
>>> "MulticastDNS");
>>
>> This can return NULL if no MulticastDNS setting is found. What
>> happens then?
>
> Nothing happens, there's a null check in resolve_set_mdns().
>
k, makes sense. I somehow missed that originally.
>>> @@ -40,6 +40,7 @@
>>> struct resolve_ops {
>>> void (*set_dns)(struct resolve *resolve, char **dns_list);
>>> void (*set_domains)(struct resolve *resolve, char
>>> **domain_list);
>>> + void (*set_mdns)(struct resolve *resolve, char *mdns);
>>
>> should probably be const char *mdns
>
> OK. Shouldn't the nearby `char **` parameters be `const char *const *`
> too, then?
>
Possibly. I think we resisted using the const variation since not many old C
hacks like to use such syntax. So we kept using 'char **'.
For passing simple C-strings we like to be const-correct though.
Regards,
-Denis
next prev parent reply other threads:[~2021-02-11 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 23:43 [PATCH] src: configure systemd-resolved's MulticastDNS= setting Daniel Lin
2021-02-11 15:59 ` Denis Kenzior
2021-02-11 18:04 ` Daniel Lin
2021-02-11 20:45 ` Denis Kenzior [this message]
2021-02-11 18:11 ` [PATCH v2] " Daniel Lin
2021-02-11 20:48 ` Denis Kenzior
2021-02-11 20:54 ` [PATCH v3] " Daniel Lin
2021-02-11 21:08 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ce451ab-0dd3-e386-391e-bc3afd8be9f8@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.