From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: Lucian Cristian <luci@powerneth.ro>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard dkms systemd
Date: Sun, 21 Oct 2018 12:12:12 +0000 [thread overview]
Message-ID: <b0nxrg6FW687Fl8Gai_Eo8VNChZfWGIxiEhhrcjdPJY9UKGgbYOTzxkzek-YZ01khNfWy76jBAsL8wtUVj0ECl3uF_nu3r6Yk_mYSpY4O28=@protonmail.ch> (raw)
In-Reply-To: <0e93f5b4-8883-57e4-0114-42f0bfd5f6c3@powerneth.ro>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, October 20, 2018 10:59 PM, Lucian Cristian <luci@powerneth.ro> wrote:
> updating the wireguard module on systemd based linux gives
>
> Warning: The unit file, source configuration file or drop-ins of
> wg-quick@wg0.service changed on disk. Run 'systemctl daemon-reload' to
> reload units.
> Sleeping 3 seconds...
>
This has nothing to do with dkms. Systemd units are part of
wireguard-tools package.
> can this be fixed int the restart script ?
>
There isn't a "restart script" in any wireguard package.
> the tunnel won't come up if the unit is not reloaded
>
Then reload it. You have exact command printed.
> Thank you !
Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-10-21 12:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 20:59 Lucian Cristian
2018-10-20 21:07 ` Robert-André Mauchin
2018-10-21 12:12 ` Jordan Glover [this message]
2018-10-21 15:49 ` Lucian Cristian
2018-11-02 13:52 ` Daniel Kahn Gillmor
2018-11-02 23:27 ` Reuben Martin
2018-11-04 3:24 ` Daniel Kahn Gillmor
2018-11-04 15:35 ` Jason A. Donenfeld
2018-11-05 6:28 ` Daniel Kahn Gillmor
2018-11-05 11:27 ` Fabian Grünbichler
2018-11-06 7:16 ` Daniel Kahn Gillmor
2018-11-06 13:04 ` Fabian Grünbichler
2018-11-07 2:29 ` Daniel Kahn Gillmor
2018-11-05 15:51 ` Jason A. Donenfeld
2018-11-03 11:54 ` Matthias Urlichs
2018-11-04 3:22 ` Daniel Kahn Gillmor
2018-10-21 13:01 ` Jonathon Fernyhough
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='b0nxrg6FW687Fl8Gai_Eo8VNChZfWGIxiEhhrcjdPJY9UKGgbYOTzxkzek-YZ01khNfWy76jBAsL8wtUVj0ECl3uF_nu3r6Yk_mYSpY4O28=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=luci@powerneth.ro \
--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).