You were right!! I had a relative path to the update.log file, so I
looked in the home path of the cron environment and found the
update.log file that the cron job was writing to. I updated my program
to point to the absolute path of the update.log file that I wanted the
logs written to, and now
<[EMAIL PROTECTED]> skrev i en meddelelse
news:[EMAIL PROTECTED]
> permissions just to be safe. What would cause the logging to work at a
> command prompt but fail in cron?
Because the environment is different; "man cron" might tell *how* it is
different (I cannot because it varies with platf
Carsten Haese wrote:
> On 23 Nov 2005 16:23:11 -0800, vagrantbrad wrote
>
>>I'm using python 2.4 running on Fedora Core 4. I have written a python
>>program called ipscan.py that checks the external ip address of my
>>cable internet connection, and on change, will update the dns records
>>at my d
On 23 Nov 2005 16:23:11 -0800, vagrantbrad wrote
> I'm using python 2.4 running on Fedora Core 4. I have written a python
> program called ipscan.py that checks the external ip address of my
> cable internet connection, and on change, will update the dns records
> at my dns provider, zoneedit. So
I'm using python 2.4 running on Fedora Core 4. I have written a python
program called ipscan.py that checks the external ip address of my
cable internet connection, and on change, will update the dns records
at my dns provider, zoneedit. So basically, I've setup dynamic dns
using python. Once th
