39

I'm running this:

os.system("/etc/init.d/apache2 restart")

It restarts the webserver, as it should, and like it would if I had run the command directly from the terminal, it outputs this:

* Restarting web server apache2 ... waiting [ OK ]

However, I don't want it to actually output it in my app. How can I disable it? Thanks!

timss
  • 9,982
  • 4
  • 34
  • 56
user697108
  • 3,521
  • 3
  • 20
  • 14
  • 5
    `os.system("/etc/init.d/apache2 restart >/dev/null")` will discard that output. As Noufal has said, `subprocess` is preferred. If you're wanting to make a quick adjustment to pre-existing code, though, redirecting to /dev/null might be an attractive option. – Kirk Strauser Apr 08 '11 at 15:09
  • 1
    @kirk: why a comment rather than a answer ? – mb14 Apr 08 '11 at 15:32
  • 1
    @mb14: I didn't think it was as "correct" as the recommendations to use subprocess. I thought of it as more of a side note, like "while I'm not exactly suggesting you do this, here's another idea." – Kirk Strauser Apr 08 '11 at 15:50
  • related: [How to hide output of subprocess in Python 2.7](http://stackoverflow.com/q/11269575/4279) – jfs Aug 12 '15 at 00:56
  • this worked for me because i was looking for something which works in python 2 and 3. – ChathuraG Aug 11 '16 at 13:37
  • You can also see is their is a quiet or silent command line option. This, however, is not garunteed, and the program may still output stderr. – Sushila Jyothi Lévêque Apr 24 '20 at 04:09

6 Answers6

64

Avoid os.system() by all means, and use subprocess instead:

with open(os.devnull, 'wb') as devnull:
    subprocess.check_call(['/etc/init.d/apache2', 'restart'], stdout=devnull, stderr=subprocess.STDOUT)

This is the subprocess equivalent of the /etc/init.d/apache2 restart &> /dev/null.

There is subprocess.DEVNULL on Python 3.3+:

#!/usr/bin/env python3
from subprocess import DEVNULL, STDOUT, check_call

check_call(['/etc/init.d/apache2', 'restart'], stdout=DEVNULL, stderr=STDOUT)
jfs
  • 399,953
  • 195
  • 994
  • 1,670
38

Depending on your OS (and that's why as Noufal said, you should use subprocess instead) you can try something like

 os.system("/etc/init.d/apache restart > /dev/null")

or (to mute also the error)

os.system("/etc/init.d/apache restart > /dev/null 2>&1")
Community
  • 1
  • 1
mb14
  • 22,276
  • 7
  • 60
  • 102
25

You should use the subprocess module using which you can control the stdout and stderr in a flexible fashion. os.system is deprecated.

The subprocess module allows you to create an object which represents a running external process. You can read it from it's stdout/stderr, write to it's stdin, send it signals, terminate it etc. The main object in the module is Popen. There are a bunch of other convenience methods like call etc. The docs are very comprehensive and include a section on replacing the older functions (including os.system).

Noufal Ibrahim
  • 71,383
  • 13
  • 135
  • 169
  • Awesome. Thanks for answering. Which function would it be though? The docs confuse me. call? popen? – user697108 Apr 08 '11 at 15:02
  • 4
    +10 for an incomplete answer! This shows that voting and quality don't go hand in hand :-) . Noufal, you could mention the differences. – user225312 Apr 08 '11 at 15:04
  • 1
    `popen` but you should take some time and read through the docs. I imagine you've only skimmed through them. They're quite clear really. – Noufal Ibrahim Apr 08 '11 at 15:04
  • 2
    Do you have a source explicitly marking it as deprecated, as opposed to "not preferred"? Guido is on record as being opposed to its removal. I'm not disagreeing with your answer - subprocess is so much nicer! - just clarifying a point. – Kirk Strauser Apr 08 '11 at 15:07
  • 1
    Guido is generally against changing the standard library. The [docs for `os.system`](http://docs.python.org/library/os.html#os.system) indicate that it's "preferable" to use subprocess. – Noufal Ibrahim Apr 08 '11 at 15:10
  • A A: I think it was fairly complete. All that was needed was a pointer to the *right* way. I'm surprised at the upvotes though. I've updated it with some more information. – Noufal Ibrahim Apr 08 '11 at 15:10
  • @AA: I think when the answer is to redirect to a doc, a quick answer is a good answer. I think Noufal answer is a good answer then (even though indeed not enough to be accepted). – mb14 Apr 08 '11 at 15:15
1

Here is a system call function I pieced together several years ago and have used in various projects. If you don't want any output from the command at all you can just say out = syscmd(command) and then do nothing with out.

Tested and works in Python 2.7.12 and 3.5.2.

def syscmd(cmd, encoding=''):
    """
    Runs a command on the system, waits for the command to finish, and then
    returns the text output of the command. If the command produces no text
    output, the command's return code will be returned instead.
    """
    p = Popen(cmd, shell=True, stdin=PIPE, stdout=PIPE, stderr=STDOUT,
        close_fds=True)
    p.wait()
    output = p.stdout.read()
    if len(output) > 1:
        if encoding: return output.decode(encoding)
        else: return output
    return p.returncode
jdgregson
  • 1,457
  • 17
  • 39
0

I was having a similar problem using a Windows machine and found this was the easiest way of fixing my problem

import subprocess
cmd='gdalwarp -overwrite -s_srs EPSG:4283 -t_srs EPSG:28350 -of AAIGrid XXXXX.tif XXXXX.asc'
subprocess.run(cmd,shell=True)

change cmd for whatever you want to run. I iterated this > 1000 times and without the command prompt window appearing, I was able to save a lot of time.

Juan Ossa
  • 1,153
  • 1
  • 10
  • 14
0

When using Python 3.5+ you can also use the newer subprocess.run(...) method and pass the capture_output=True option:

import subprocess
subprocess.run(['/etc/init.d/apache2', 'restart'], capture_output=True)

See the examples in the using-the-subprocess-module section in the docs in case you actually want to capture the output.

luigisuncorner
  • 51
  • 4