From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] network/lib6/getaddrinfo01: rewrite with the new API + use static hostnames
Date: Wed, 19 May 2021 21:59:34 +0200 [thread overview]
Message-ID: <YKVuJksJkHh7uxbX@pevik> (raw)
In-Reply-To: <b7744613-ee02-c4a5-e5ed-da3da60a6e7b@bell-sw.com>
> On 18.05.2021 22:15, Petr Vorel wrote:
> > Hi Alexey,
> > ...
> >> +static void setup(void)
> >> +{
> >> + unsigned int i;
> >> + int fd;
> > ...
> >> + SAFE_CP(host_file, "hosts");
> > One more thing, could we check for /etc/hosts before?
> Hi Petr,
> Yes, why not. I assume it can be read-only, but I hope we won't hide a
> configuration bug with this...
Hi Alexey,
hm, not sure if we can hide configuration bug. For a traditional distros
probably yes, but not for embedded and other special distros.
And good point, I'd TCONF also when file is read-only (which is more likely that
file not presented). We can always think about different solution if anybody
complains about this requirement.
Kind regards,
Petr
> > Because we want to TCONF on systems without it not TBROK.
> > And I guess there are embedded systems without it out there.
> > Kind regards,
> > Petr
next prev parent reply other threads:[~2021-05-19 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 9:14 [LTP] [PATCH] network/lib6/getaddrinfo01: rewrite with the new API + use static hostnames Alexey Kodanev
2021-05-18 9:22 ` [LTP] [PATCH v2] " Alexey Kodanev
2021-05-18 15:20 ` Petr Vorel
2021-05-18 19:15 ` [LTP] [PATCH] " Petr Vorel
2021-05-19 7:32 ` Alexey Kodanev
2021-05-19 19:59 ` Petr Vorel [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-17 8:56 Alexey Kodanev
2021-05-17 19:57 ` Petr Vorel
2021-05-18 10:19 ` Alexey Kodanev
2021-05-18 9:59 ` Cyril Hrubis
2021-05-18 6:02 ` Petr Vorel
2021-05-18 8:30 ` Alexey Kodanev
2021-05-18 15:25 ` Petr Vorel
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=YKVuJksJkHh7uxbX@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox