speed container creation/destruction

As the state of the container is monitored with the netlink, the file state is no longer used to watch the state changes. The previous hack, which adds a tempo of 200ms, is removed and that makes the container being created, started, stopped, destroyed faster, we gain 1 second in a container lifecycle. One second is too much if we launch thousand of containers, one by one like for example in a tests suite. Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

speed container creation/destruction
34e7030e · Daniel Lezcano · 3f21c114 · 34e7030e
Commit 34e7030e authored Mar 31, 2009 by Daniel Lezcano
Show whitespace changes
Inline Side-by-side

Showing with 0 additions and 7 deletions

state.c src/lxc/state.c +0 -7

No files found.
--- a/src/lxc/state.c
+++ b/src/lxc/state.c
@@ -93,13 +93,6 @@ out:
 	lxc_monitor_send_state(name, state);
-	/* let the event to be propagated, crappy but that works,
-	 * otherwise the events will be folded into only one event,
-	 * and I want to have them to be one by one in order
-	 * to follow the different states of the container.
-	 */
- 	usleep(200000);
 	return -err;
 }