Fixing RM.DEPLOY being executed after/during RM.RELEASE by adding a release_lock...

[nepi.git] / src / nepi / resources / linux / tcpdump.py

diff --git a/src/nepi/resources/linux/tcpdump.py b/src/nepi/resources/linux/tcpdump.py
index e9955f4..12d11a2 100644 (file)
--- a/src/nepi/resources/linux/tcpdump.py
+++ b/src/nepi/resources/linux/tcpdump.py
@@ -18,7 +18,7 @@
 # Author: Alina Quereilhac <alina.quereilhac@inria.fr>
 
 from nepi.execution.attribute import Attribute, Flags, Types
-from nepi.execution.resource import clsinit_copy, failtrap 
+from nepi.execution.resource import clsinit_copy 
 from nepi.resources.linux.application import LinuxApplication
 from nepi.util.timefuncs import tnow
 
@@ -316,8 +316,7 @@ class LinuxTcpdump(LinuxApplication):
         self._home = "tcpdump-%s" % self.guid
         self._sudo_kill = True
 
-    @failtrap
-    def deploy(self):
+    def do_deploy(self):
         if not self.get("command"):
             self.set("command", self._start_command)
 
@@ -327,7 +326,7 @@ class LinuxTcpdump(LinuxApplication):
         if not self.get("depends"):
             self.set("depends", "tcpdump")
 
-        super(LinuxTcpdump, self).deploy()
+        super(LinuxTcpdump, self).do_deploy()
 
     @property
     def _start_command(self):