Public bug reported:
-(cmsj@tenshu)-(~)- sudo ifup --allow auto lolif0
-(cmsj@tenshu)-(~)- sudo ifdown --allow auto lolif0
ifdown: interface lolif0 not configured
-(cmsj@tenshu)-(~)-
ifdown should be quiet here, like ifup is. Otherwise upstart's
network-interface.conf job may cause a log file to be created in
/var/log/upstart/ for each network interface that is removed from the system
without having ever been in /e/n/i.
(for example on a cloud VM host, where TAP interfaces are being
created/destroyed with some gusto).
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ifupdown 0.7.44ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Tue Apr 1 17:48:37 2014
InstallationDate: Installed on 2013-10-21 (161 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64
(20131016)
MarkForUpload: True
SourcePackage: ifupdown
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300885
Title:
ifdown should be quiet when called by network-interface.conf upstart
job
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1300885/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
