kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Dan Kegel, would utilizing the Raring enablement stack in Precise work
for you as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack ?

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1065589

Title:
  "initctl list" shows 11974 instances of network-interface-security
  after two days of uptime

Status in “linux” package in Ubuntu:
  Incomplete
Status in “lxc” package in Ubuntu:
  Fix Released

Bug description:
  On an Ubuntu 12.04.1 system, each time you start and stop a container,
  "initctl status" shows two more instances of network-interface and network-interface-security running.
  The numbers do not go down after the container shuts down.
  Evidently there's an interface leak in lxc-start?

  Here's how I ran into this.
  Hosting a small number of buildbots in 
  one-shot ephemeral LXC containers,
  in which the LXC container is stop and started after each build,
  after two days of uptime, running the commands

  while true
  do
     time initctl list | awk '{print $1}' | sort | uniq -c | sort -n | tail -n 3
  done

  outputs

        1 wait-for-state
     6003 network-interface
    11990 network-interface-security

  real    0m19.428s

        1 wait-for-state
     6004 network-interface
    11994 network-interface-security

  real    0m19.271s

  If I stop the buildbots, the numbers stop rising.

  This broke my build.

  I can work around this by rebooting every night, but I'd sure rather
  not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065589/+subscriptions