Okay, I'm trying without the Update_file.sh /etc/crontab then...
I'll keep you informed... Thanks --- alan walters <[EMAIL PROTECTED]> a écrit : > I can confirm if you are using full updates crontab > is being updated. Well it is being replaced on my > system. I have some checks that I have to keep > reinstalling in there due to changes > > -----Original Message----- > From: Frimmel, Ivan (ISS South Africa) > [mailto:[EMAIL PROTECTED] > Sent: 08 December 2005 12:31 > To: [email protected] > Subject: RE: [pfSense Support] DynDns scheduling > issues > > As far as I know Crontab is one of the files that is > not touched during upgrades.. That's why you have to > do it manually with update_file.sh. > > So no you don't have to do it after the upgrade. > > Ivan. > > > -----Original Message----- > From: Damien Dupertuis [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 08, 2005 11:16 AM > To: [email protected] > Subject: RE: [pfSense Support] DynDns scheduling > issues > > Hello again :-) > > I upgraded to 95.4 > > Do I have to do the "Update_file.sh /etc/crontab and > reboot" > or is it included with the upgrade??? > > regards > > Damien > > > > --- Damien Dupertuis <[EMAIL PROTECTED]> a écrit : > > > Hello, > > > > Okay it works for me!!!! > > > > Thank you... > > > > > > > > > > > > --- "Frimmel, Ivan (ISS South Africa)" > > <[EMAIL PROTECTED]> a écrit : > > > > > Update_file.sh /etc/crontab and reboot > > > > > > > > > -----Original Message----- > > > From: Damien Dupertuis > > [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, December 01, 2005 7:03 AM > > > To: [email protected] > > > Subject: Re: [pfSense Support] DynDns scheduling > issues > > > > > > Hello, > > > > > > I'm using 95.a and I just got my dyndns account > banned... sorry I > > > don't have time to put the logs here... I'll do > it tomorrow... > > > > > > regards > > > > > > --- Damien Dupertuis <[EMAIL PROTECTED]> a > écrit > > : > > > > > > > Hello, > > > > > > > > just for the record, here are my system logs > > from > > > 94.12, if ever... It > > > > is not upgrading the adress properly... > > > > > > > > I'll upgrade to 0.95.a and keep you > informed... > > > > > > > > regards... > > > > > > > > Damien > > > > > > > > > > > > > > > > --- Scott Ullrich <[EMAIL PROTECTED]> a écrit > : > > > > > > > > > Please upgrade to 0.95.a > > > > > > > > > > On 11/29/05, Xtian <[EMAIL PROTECTED]> wrote: > > > > > > Howdy, > > > > > > > > > > > > I'm on .94.12 (fresh install), did the > > > following > > > > > as well: > > > > > > > > > > > > - update_file.sh /etc/inc/dyndns.class > > > > > > - Remove the cache file in > > > /cf/conf/dyndns.cache > > > > > (was not there, since new > > > > > > install) > > > > > > - update_file.sh /etc/crontab > > > > > > > > > > > > Dyndns still does bad stuff: > > > > > > > > > > > > Date: Tue, 29 Nov 2005 18:24:16 -0500 > (EST) > > > > > > From: DynDNS Support <[EMAIL PROTECTED]> > > > > > > To: xxx > > > > > > Subject: Hostname Blocked Due To Abuse > > > > > > > > > > > > Dear Valued Customer: > > > > > > > > > > > > The hostname, xxx.dyndns.org, in account > > xxx, > > > > has > > > > > been > > > > > > blocked for abuse. This action has been > > taken > > > > due > > > > > to the receipt > > > > > > of multiple updates originating from the > > same > > > IP > > > > > address. > > > > > > > > > > > > Please note, updates which result in the > IP > > > > > address associated > > > > > > with a host changing are NOT considered > > > abusive. > > > > > Only those > > > > > > updates which result in no change to the > > host > > > > are > > > > > abusive. > > > > > > Please take a moment to review our Update > > > Abuse > > > > > Policy here: > > > > > > > > > > > > http://www.dyndns.com/support/abuse.html > > > > > > > > > > > > It is vital that you correct the problem > > which > > > > is > > > > > resulting in > > > > > > these repeated and unnecessary updates. > Once > > > you > > > > > have corrected > > > > > > this problem, you may request the host be > > > > > unblocked at the > > > > > > following URL: > > > > > > > > > > > > etc. etc. > > > > > > > > > > > > > > > > > > So, I took a look at the crontab for > dyndns, > > > and > > > > > it was thusly: > > > > > > > > > > > > * */20 * * * root > /usr/bin/nice > > > > -n20 > > > > > /etc/rc.dyndns.update > > > > > > > > > > > > According to cron's manpage: > > > > > > > > > > > > Step values can be used in > > conjunction > > > > > with ranges. Following a range > > > > > > with ''/<number>'' specifies skips > > of > > > > the > > > > > number's value through the > > > > > > range. For example, ''0-23/2'' > > > > can > > > > > be used in the hours field to > > > > > > specify command execution every > > other > > > > hour > > > > > (the alternative in the V7 > > > > > > standard is > > > > > ''0,2,4,6,8,10,12,14,16,18,20,22''). Steps > > are > === message truncated === ___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
