Search found 3 matches
- April 11th, 2010, 4:25 pm
- Forum: Post-Processing Scripts
- Topic: Capturing output during a post-processing script
- Replies: 2
- Views: 3069
Re: Capturing output during a post-processing script
I figured out what the problem was. I made a bad assumption about what the working directory was when a post-processing script is run. I thought it was the directory where the script is located...it's not. For me, it was /usr/bin. Because of that, it forced my script into a function where it nee...
- April 10th, 2010, 9:01 pm
- Forum: Post-Processing Scripts
- Topic: Capturing output during a post-processing script
- Replies: 2
- Views: 3069
Re: Capturing output during a post-processing script
When I run the script from the shell, I run it as ./tvdb.py 'arg' 2 '' The single quotes are included on the command line because they have spaces in them. I don't provide all 6 arguments because I only need the 1st and 3rd. The first line of the script is #!/usr/bin/python. Here's the log entry w...
- April 10th, 2010, 1:57 pm
- Forum: Post-Processing Scripts
- Topic: Capturing output during a post-processing script
- Replies: 2
- Views: 3069
Capturing output during a post-processing script
Hi, I have a python script that I am trying to run. It runs fine when I run it from the shell. However, it's not doing anything when SABnzbd+ starts it. The script is being executed but it appears to just keep running and running forever. When I try to look at the script output, I get an error o...