incorrect month returned on 'bind time'

ashtaroth · Post by **ashtaroth** » Wed Oct 06, 2004 4:22 am

Hi all,

Just been messing with a procedure that is setup on a bind time and am experiencing an issue where the date is one month behind. I have checked my system clock and that is all sweet. When I use clock to get the time it returns all the correct data, but the actual procedure is not returning the month correctly. I have pasted some info to help if my above explanation is a little confusing...

I have the bind setup as:
bind time - "?? * * * *" show_newday

with the simple procedure:
proc show_newday { min hour day month year } {
putmsg ashtaroth "$min $hour $day $month $year"
}

Current system time:
Wed Oct 06 08:06:27 AM UTC 2004

Procedure returns:
06 08 06 09 2004

I have checked that Oct = 10 about 5 times to ensure I am not making a total jack out of myself

Would be interested if anyone could enlighten me on why this might be happening. Whether it is my own stupidity or a legit bug.

Thanks.
ash.

Alchera · Post by **Alchera** » Wed Oct 06, 2004 6:58 pm

Check these settings in your eggdrop configuration:

Code: Select all

set timezone "CST"

set offset "5"

You need to know the time zone (GMT+/-) of the bots' physical location. Might solve your problem.

awyeah · Post by **awyeah** » Wed Oct 06, 2004 9:05 pm

Search up [ctime], [unixtime], [duration], [clock], [format] in tcl-commands.doc and use those, according the the format you want to return your date/time in. They are much better and give accurate information, no matter what timezone you have set in the bots configuration file.

Alchera · Post by **Alchera** » Thu Oct 07, 2004 12:36 am

awyeah wrote:no matter what timezone you have set in the bots configuration file.

Really?

awyeah · Post by **awyeah** » Thu Oct 07, 2004 3:33 am

I guess so, mine works fine.

Alchera · Post by **Alchera** » Sat Oct 09, 2004 7:30 pm

I use a script that gets time/date information and believe me if I do not have the setting in the bots' configuration correctly set it can be way out. The reason being time zone selection. The information is taken from where the bot physically is.