From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Lucian Cristian <luci@powerneth.ro>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard dkms systemd
Date: Fri, 02 Nov 2018 09:52:19 -0400 [thread overview]
Message-ID: <87pnvnmvsc.fsf@fifthhorseman.net> (raw)
In-Reply-To: <17a30c81-d413-a742-77a7-8743b2574a3c@powerneth.ro>
On Sun 2018-10-21 18:49:19 +0300, Lucian Cristian wrote:
> is an annoyance to restart it manually, if you are inside the vpn, you
> can't do it, I thought that there is a restart script at package update..
as a packager (debian, not ubuntu, but priniciples might be similar
across operating systems), i'm very leery to automatically restart
services during an upgrade, particularly when those services might
affect the connectivity of the system administrator who is doing the
upgrade.
that means i'm unlikely automatically restart network interfaces in a
package's postinst (post-installation script). And, since another
package could also be in the process of updating systemd units, i'm also
unlikely to automatically issue a "systemctl daemon-reload" in postinst.
if you want "systemd daemon-reload" to happen after successful package
installation, that would probably be a job for the package manager
itself (in debian and ubuntu, that's probably apt (or maybe dpkg)), or
for hooks/triggers associated with package management.
If anyone has a robust/reliable solution that's not likely to cause the
kinds of problems i'm concerned about, i'd love to hear it.
--dkg
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-11-02 23:01 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
2018-10-21 15:49 ` Lucian Cristian
2018-11-02 13:52 ` Daniel Kahn Gillmor [this message]
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=87pnvnmvsc.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--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).