Search found 7 matches
- 23 Mar 2017, 13:59
- Forum: Scripting and Automation
- Topic: Curl in --def exec - Getting: sh: 1: curl: not found
- Replies: 6
- Views: 3919
Re: Curl in --def exec - Getting: sh: 1: curl: not found
Debian package did the trick. Curl is working, as are the other commands. Additionally, Filebot will now read and write to my drives mounted in /media/<USER>, as I was running into permission issues there as well, but managed to get around it by mounting the drives somewhere else. So that's a bonus ...
- 23 Mar 2017, 12:43
- Forum: Scripting and Automation
- Topic: Curl in --def exec - Getting: sh: 1: curl: not found
- Replies: 6
- Views: 3919
Re: Curl in --def exec - Getting: sh: 1: curl: not found
I mentioned I installed Filebot with Ubuntu Software - it must have installed the snap package. Just assumed it was part of filebot, not a package thing - I'm obviously new to linux. If there's a preferred way to install on Linux that might be easier to get working, I'm all for it. filebot -script ...
- 23 Mar 2017, 11:50
- Forum: Scripting and Automation
- Topic: Curl in --def exec - Getting: sh: 1: curl: not found
- Replies: 6
- Views: 3919
Re: Curl in --def exec - Getting: sh: 1: curl: not found
date; whoami Execute: date; whoami Thu Mar 23 22:25:42 AEDT 2017 sh: 1: whoami: Permission denied Done ヾ(@⌒ー⌒@)ノ which curl Processed 1 files Execute: which curl Done ヾ(@⌒ー⌒@)ノ printenv - I've replaced my username with "<USER>" Execute: printenv LESSOPEN=| /usr/bin/lesspipe %s GNOME_KEYRING_PID= USER ...
- 23 Mar 2017, 09:51
- Forum: Scripting and Automation
- Topic: Curl in --def exec - Getting: sh: 1: curl: not found
- Replies: 6
- Views: 3919
Curl in --def exec - Getting: sh: 1: curl: not found
I think this might be a Linux permission or path problem, rather than a Filebot one, but I figured I'd try here, seeing as I've really got no idea at this point. My error: sh: 1: curl: not found I installed Filebot 4.7.8 using the software manager on Ubuntu 16.04 LTS. Curl is working perfectly when ...
- 27 Feb 2017, 00:14
- Forum: Scripting and Automation
- Topic: Getting "The token '&&' is not a valid statement separator in this version." error.
- Replies: 1
- Views: 8262
Getting "The token '&&' is not a valid statement separator in this version." error.
I recently updated to the windows app version of Filebot, which I'm calling from a batch script. Although I'm now getting an error due to the "&&" in my--def exec string. This was working with the previous non-windows app version of Filebot. Is there another "token" I need to be using? The error: At ...
- 26 Oct 2016, 01:10
- Forum: Scripting and Automation
- Topic: "-conflict auto" with file data in filename.
- Replies: 2
- Views: 1962
Re: "-conflict auto" with file data in filename.
Ah, fantastic. All the hard work is done. Thanks heaps Red!
- 25 Oct 2016, 09:57
- Forum: Scripting and Automation
- Topic: "-conflict auto" with file data in filename.
- Replies: 2
- Views: 1962
"-conflict auto" with file data in filename.
I'm having trouble with the "-conflict auto" command within the AMC script, due to how I name my files. My file name expression results in a filename like this: The Blacklist - S04E05 - The Lindquist Concern [720p.HDTV.AVC.AC3.5.1] When a better file is downloaded and renamed, the file sometimes has ...