Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Tony Finch <dot@dotat.at>
To: wireguard@lists.zx2c4.com
Subject: Re: [PATCH] wg: include filename in error messages
Date: Tue, 30 Apr 2024 13:36:51 +0100	[thread overview]
Message-ID: <22ae9383-52b4-6136-e52c-18e1b73d7d40@dotat.at> (raw)
In-Reply-To: <a0fe98b4-15a5-a60b-9eb2-2c721e60dd6d@dotat.at>

Yesterday when I was setting up wireguard using ifupdown, I got a "file
not found" error which mentioned neither the program nor the filename, so
I was at a loss. After making ifupdown more verbose the problem turned out
to be wireguard.

When I was preparing this patch I really wanted to change all the error
reporting to use err(3) because in my experience it's reasonably nice for
the programmer and the user. Dunno if err(3) counts as part of a sane libc
or if it's worth spending time on such a patch?

-- 
Tony Finch  <dot@dotat.at>  https://dotat.at/
Fair Isle, Faeroes: Variable 2 to 4 in west Faeroes at first,
otherwise southeasterly 4 to 6. Moderate, occasionally rough at first
in east Fair Isle. Showers, fog patches later. Good, occasionally very
poor later.

      reply	other threads:[~2024-11-18 13:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 12:25 Tony Finch
2024-04-30 12:36 ` Tony Finch [this message]

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=22ae9383-52b4-6136-e52c-18e1b73d7d40@dotat.at \
    --to=dot@dotat.at \
    --cc=wireguard@lists.zx2c4.com \
    /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;
as well as URLs for NNTP newsgroup(s).