X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from dal-a2.localdomain (unknown [74.117.189.115]) by mail.alpinelinux.org (Postfix) with ESMTP id 599F4DC0081 for ; Thu, 1 Aug 2013 06:31:55 +0000 (UTC) Received: from ncopa-desktop.alpinelinux.org (3.203.202.84.customer.cdi.no [84.202.203.3]) (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ncopa@tanael.org) by dal-a2.localdomain (Postfix) with ESMTPSA id B6D80BC2DC3 for ; Thu, 1 Aug 2013 06:31:54 +0000 (UTC) Date: Thu, 1 Aug 2013 08:31:50 +0200 From: Natanael Copa To: alpine-devel@lists.alpinelinux.org Subject: [alpine-devel] Feature for NETDOWN=no Message-ID: <20130801083150.6b41dbab@ncopa-desktop.alpinelinux.org> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.20; x86_64-unknown-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, I got a feature request for preventing taking down an interface on shutdown. I wonder how we should implement this. Option 1: set RC_NETDOWN=no in /etc/rc.conf (or /etc/conf.d/networking) will prevent taking down all the network interface on shutdown. No support for preventing individual interfaces - its all or nothing. Option 2: Use a blacklist (eg RC_PREVENT_NETDOWN) of interfaces to not take down. For example: RC_PREVENT_NETDOWN="eth0 eth3" will take down eth1 and eth2 but not eth0 and eth3. If set to 'all', all interfaces will be kept up and if set to 'none' all interfaces will be taken down. Deafult would be 'none'. Alternative variable names are: RC_NET_KEEP_UP Option 3: Use a whitelist of interfaces to take down on shutdown. For example RC_NETDOWN="eth1 eth2" will keep eth0 and eth3 up on shutdown. If set to 'all' then all interfaces will be taken down and if set to 'none', all interfaces will be kept up on shutdown. Default would be 'all'. What do you prefer? They are all very simple to implement. What are good variable names? -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---