We actually do want to run the configured system commands on the shell, so set shell to True
Also includes a workaround for sarge bug no. 21 Closes #489
This commit is contained in:
parent
9d69951faa
commit
d4e7c2e1b1
1 changed files with 6 additions and 1 deletions
|
|
@ -161,7 +161,12 @@ def performSystemAction():
|
|||
if availableAction["action"] == action:
|
||||
logger.info("Performing command: %s" % availableAction["command"])
|
||||
try:
|
||||
p = sarge.run(availableAction["command"], stderr=sarge.Capture())
|
||||
# Note: we put the command in brackets since sarge (up to the most recently released version) has
|
||||
# a bug concerning shell=True commands. Once sarge 0.1.4 we can upgrade to that and remove this
|
||||
# workaround again
|
||||
#
|
||||
# See https://bitbucket.org/vinay.sajip/sarge/issue/21/behavior-is-not-like-popen-using-shell
|
||||
p = sarge.run([availableAction["command"]], stderr=sarge.Capture(), shell=True)
|
||||
if p.returncode != 0:
|
||||
returncode = p.returncode
|
||||
stderr_text = p.stderr.text
|
||||
|
|
|
|||
Loading…
Reference in a new issue