On Tue, Apr 17, 2018 at 4:11 PM, wrote:
> W dniu sobota, 27 stycznia 2018 16:59:50 UTC+1 użytkownik larry@gmail.com
> napisał:
>> I have a script that does this:
>>
>> subprocess.Popen(['service', 'some_service', 'status'],
>> stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
>>
>> When I ru
W dniu sobota, 27 stycznia 2018 16:59:50 UTC+1 użytkownik larry@gmail.com
napisał:
> I have a script that does this:
>
> subprocess.Popen(['service', 'some_service', 'status'],
> stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
>
> When I run it from the command line it works fine. When I r
On Sat, 27 Jan 2018 10:58:36 -0500, Larry Martell wrote:
> I have a script that does this:
>
> subprocess.Popen(['service', 'some_service', 'status'],
> stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
>
> When I run it from the command line it works fine. When I run it from
> cron I get:
>
>
On Sat, Jan 27, 2018 at 11:09 AM, Chris Angelico wrote:
> On Sun, Jan 28, 2018 at 2:58 AM, Larry Martell
> wrote:
>> I have a script that does this:
>>
>> subprocess.Popen(['service', 'some_service', 'status'],
>> stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
>>
>> When I run it from the com
If you have your script set $PATH and $HOME, you can test it with:
env - ./my-script
The difference between running a script from the command line, and
running a script from cron, is often environment variables. env -
clears the environment.
On Sat, Jan 27, 2018 at 7:58 AM, Larry Martell wrote:
On 2018-01-27, Larry Martell wrote:
> I have a script that does this:
>
> subprocess.Popen(['service', 'some_service', 'status'],
> stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
>
> When I run it from the command line it works fine. When I run it from
> cron I get:
>
> subprocess.Popen(['s
On Sun, Jan 28, 2018 at 2:58 AM, Larry Martell wrote:
> I have a script that does this:
>
> subprocess.Popen(['service', 'some_service', 'status'],
> stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
>
> When I run it from the command line it works fine. When I run it from
> cron I get:
>
> su
I have a script that does this:
subprocess.Popen(['service', 'some_service', 'status'],
stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
When I run it from the command line it works fine. When I run it from
cron I get:
subprocess.Popen(['service', 'some_service', 'status'],
stdout=subproces