egghelp/eggheads community

problems with bseen script! [user] was last seen only -90502

2001-11-12T20:21:00-04:00

This is correct. It was down to a date issue.

As you should know, unixtime is stored and read as seconds since epoc (crap, when was that, can't remember).

In C, you have to set the size of a variable, 1 size too many for the data you are going to handle, as a null terminator is used at the end, and as such, is part of the strings length.

When the size of the number increased an extra digit in september, it caused problems on some systems.

This was fixed way back, between 1.6.4 and 1.6.5, but was never very well publicised until a few weeks before the bug was due to occur.

A simple upgrade is all that is needed to fix the issue, or placing the following 3 lines at the bottom of your config file

proc unixtime {} {
return [clock seconds]
}

Statistics: Posted by ppslim — Mon Nov 12, 2001 8:21 pm

problems with bseen script! [user] was last seen only -90502

2001-11-12T18:30:00-04:00

thanks!
that solved the problem.

Statistics: Posted by Guest — Mon Nov 12, 2001 6:30 pm

problems with bseen script! [user] was last seen only -90502

2001-11-12T17:06:00-04:00

I had this problem as well with 1.6.4. Upgrading to 1.6.6 solved the issue. My belief at the time was it was caused by the date bug which was documented on the front page here back when it surfaced and became an issue.

later
P

Statistics: Posted by Guest — Mon Nov 12, 2001 5:06 pm

problems with bseen script! [user] was last seen only -90502

2001-11-12T15:55:00-04:00

hi
i got this strange problem with my bseen script. it seems like it counts the time since a user left the chan 10 times too slow or it prints a message like this one:

crnholio, [user] was last seen on @bot/#chan only -905027966 seconds ago.

could somebody help me please? it ssems like its a failure in the user-file, because the failure is on the whole botnet (2bots )

Statistics: Posted by Guest — Mon Nov 12, 2001 3:55 pm