Your message dated Sat, 26 Dec 2015 11:37:42 +0100
with message-id <[email protected]>
and subject line Re: Bug#84074: ifupdown state was moved to /run
has caused the Debian Bug report #84074,
regarding ifupdown: --force should work even when ifstate is not writable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
84074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84074
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifupdown
Version: 0.6.4-3
Severity: normal
If the ifstate file cannot be written to, ifup and ifdown should not
fail, but only print a warning about this (I'd compare this to the
behaviour of mount wrt /etc/mtab)
For now I can't ifdown an iface if / has been remounted R/O for
maintainance (well, calling ifconfig directly does help, but ifupdown
has a purpose, isn't it :)
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux bylbo 2.2.18 #1 Wed Dec 20 23:25:48 CET 2000 i586
Versions of packages ifupdown depends on:
ii libc6 2.2.1-1 GNU C Library: Shared libraries an
ii net-tools 1.57-1 The NET-3 networking toolkit
--- End Message ---
--- Begin Message ---
Version: 0.7~beta2
On Fri, Dec 25, 2015 at 08:58:34PM -0800, Elliott Mitchell wrote:
> What was previously in /etc/network/run was moved to /run/network a while
> ago. This seems to accomplish what the wishlist bug #84074 was about,
> perhaps it should be closed now?
Indeed, thanks.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
