Skip to main content

Python subprocess run local commands

Python subprocess module is quite helpful in running local commands. While Fabric module can also be used to run local commands, Fabric module is overkill to run local commands on the system. Fabric module is quite useful in running commands on remote system via SSH.

Whereas subprocess mnodule is quite ideal to execute local commands on the VM, device or local server.

Python code example below to run local commands with try exception to capture any errors.

Code below will run the "xz" command to zip the file on the specified path.
xz command will replace the specified file as an xz file. xz file won't create a new file.
import subprocess

try:
 # Run the xz command
 subprocess.run(['xz', '/tmp/app_log.log'], check=True)

 print("File successfully compressed.")

except subprocess.CalledProcessError as e:
    print(f"Error: Command failed with exit status {e.returncode}")

except FileNotFoundError:
    print("Error: xz command not found. Ensure xz is installed.")

Sample image output:

Python code below uses "tar" command to zipped the file and it doesn't use any try exception to capture any errors but the code will display any errors captured.

Error will likely occur, if the path requires a root elevation and Python program is not executed without any proper privileges.

Or it will also show an error, if the Tar syntax is wrong.

When using Tar, you must specify both the name of the compressed file to be created and the path or location of the file to compress. The compressed file’s name does not need to match the name of the original file.

Unlike "xz" command, tar will not replace the file but will create a new file.
With the tar command the existing file will still be there but will just create zipped backup file.

For xz command, the original file will be zipped and won't create a new one.

In summary, Tar is used for creating backups, while xz compresses files to save storage space. Choice is yours.
Example code below runs a Tar command, using Python subprocess module.
import subprocess

# Run the tar command
 capture_result = subprocess.run(['tar', 'czvf', '/tmp/app_log.log.tar.gz', '/tmp/app_log.log'], check=True)

 # Print the output and errors (if any)
 print("Output: [check output if successful or not]")
 print(capture_result.stdout)

 print("Errors:")
 print(capture_result.stderr)

 # Print the return code
 print("Return Code:", capture_result.returncode)


Sample image output:







Do what is right and good before the eyes of God. Be righteous and look forward for the things in Heaven.
The world you inhabit and the things you cherish are but a passing shadow.
Proverbs 15:9: "The way of the wicked is an abomination to the Lord, but He loves him who pursues righteousness."

Comments

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...