From: Jeffrey Walton <noloader@gmail.com>
To: Eryk Wieliczko <eryk@wieliczko.ninja>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: DNS name resolution should not be done during configuration parsing.
Date: Sun, 17 Feb 2019 08:07:13 -0500 [thread overview]
Message-ID: <CAH8yC8nz5wwL=xKipUwUtrMqQJ5fHcWAdwzrMpX0Hxck+gO0kQ@mail.gmail.com> (raw)
In-Reply-To: <CHanFQf0BHc_tN8WFKYbpEbjSNMTveoCt1-zENLXnF_XJpdYLN4ywKtkwQ9mjdEYd55O4fQyMNHwRozH7Qi30CjTkiuUO_nPsHNLe_D5EyI=@wieliczko.ninja>
On Sun, Feb 17, 2019 at 7:40 AM Eryk Wieliczko <eryk@wieliczko.ninja> wrote:
> > Forgive my ignorance... Should init just retry the service start?
> > Something like this (from Systemd):
> >
> > [Unit]
> > StartLimitInterval=360
> > StartLimitBurst=5
> >
> > The statements above say to retry 5 times within 360 seconds.
> Configuring such things is an additional unnecessary step. OpenVPN/tinc don't require such hacks. Once you start OpenVPN, it's gonna work until the server dies of old age. :-)
I have to admit I don't quite understand calling it "unnecessary".
There seems to be two use cases (maybe more?): manual start and auto
start. The auto start case is usually handled by init scripts. Init
scripts usually retry.
I'm not throwing stones, but I have to ask... Why not use the tools
available instead of adding hacks on top of hacks? The hacks likely
make the code brittle. By the time Wiregaurd gets to supporting AIX,
Dragonfly, Hurd, Solaris and other Unix personalities no one will want
to touch it.
Jeff
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-02-18 23:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 22:28 Eryk Wieliczko
2019-02-17 3:03 ` David Kerr
2019-02-17 4:08 ` Jeffrey Walton
2019-02-17 12:40 ` Eryk Wieliczko
2019-02-17 13:07 ` Jeffrey Walton [this message]
2019-02-17 13:15 ` Eryk Wieliczko
2019-02-19 3:01 ` zrm
2019-02-19 7:22 ` Matthias Urlichs
2019-02-19 14:26 ` Lonnie Abelbeck
2019-02-19 15:45 ` Vincent Wiemann
2019-02-21 7:59 ` Matthias Urlichs
2019-02-22 1:29 ` Vincent Wiemann
2019-02-19 14:58 ` David Kerr
2019-02-17 12:47 ` Eryk Wieliczko
2019-02-17 18:26 ` Vincent Wiemann
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='CAH8yC8nz5wwL=xKipUwUtrMqQJ5fHcWAdwzrMpX0Hxck+gO0kQ@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=eryk@wieliczko.ninja \
--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).