All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] openvpn: fix init script name
Date: Sat, 19 Jan 2013 11:21:24 +0100	[thread overview]
Message-ID: <50FA73A4.4080304@mind.be> (raw)
In-Reply-To: <87mww9mu8k.fsf@dell.be.48ers.dk>

On 16/01/13 09:01, Peter Korsgaard wrote:
> You could argue that we should make the order somewhere between 45
> (networkmanager/connman) and 50 (network servers) so you could make the
> network servers listen on the vpn interface.

  It sounds logical that VPN is started before the network servers.

  OTOH most servers listen on all interfaces anyway so it shouldn't make 
a difference.

  And anyway, the openvpn --daemon will exit immediately, long before the 
new tun/tap interface actually appears. So it makes no sense to consider 
anything to depend on openvpn.

  On Debian, openvpn depends on network, nfs-client and syslog, and is 
started before X. Cups and samba are started after openvpn, but ftpd, 
apache and exim4 are started before.

  Bottom line: keep it as it is, since it doesn't make a big difference.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2013-01-19 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 20:34 [Buildroot] [git commit] openvpn: fix init script name Peter Korsgaard
2013-01-15 23:22 ` Steve Calfee
2013-01-16  8:01   ` Peter Korsgaard
2013-01-19 10:21     ` Arnout Vandecappelle [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=50FA73A4.4080304@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.