sitewho.exe by ADDiCT

[ADDiCT]

aah yes, forgot to update the old templates with the new cookies :
%(usercount) is now %(usercountall)

[ADDiCT]

updates in 1.0.6
- extended time cookies (requested by Bounty ) --> readme.nfo for more details !
- fixed old cookies in default templates

[ADDiCT]

updates in 1.0.7 :
- correct checking if (matching) users are online or not (previous version could output header + footer without body if hidden users were online)
- 'nobody' templates for uploaders/downloaders/idlers

[MaistroX]

Nice .

[bounty]

Originally posted by ADDiCT
updates in 1.0.7 :
- correct checking if (matching) users are online or not (previous version could output header + footer without body if hidden users were online)
- 'nobody' templates for uploaders/downloaders/idlers

W00T !! this one really roxx
big thx

bounty

[odd]

Test on previous version and this new verison. Logintime isnt correct. Check idle time against logintime, idletime shouldnt be a minut before logintime.

site swho idle
Right after login:
200-| Logintime: 0d 0h 0m -30s Idletime: 0d 0h 0m 0s

After 10 sec:
200-| Logintime: 0d 0h 0m -20s Idletime: 0d 0h 0m 10s

What ive used in tamplete's, Ive changed them to my desire but it should be working anyway.
| | Logintime: %(logintime_total_d)d %(logintime_h)h %(logintime_m)m %(logintime_s)s Idletime: %(idletime_total_d)d %(idletime_h)h %(idletime_m)m %(idletime_s)s (lastcmd)

Ive set time_offset = 3630 and that gives me exact idle time for the users. But the logintime is incorrect.

[ADDiCT]

logintime is correct, idletime is wrong

please leave time_offset to a mulitple of 3600, as that's definately not going to help

so if you leave it to 3600, logintime = 0s and idletime = 30s ?

[odd]

Hmm odd. Ive had problem before with the idle time was not correct and when ive change the time_offset to 3630 idletime was perfect.
Ive changed back as u said and login and idle is perfect. Hehe my misstake :>

[romracer]

I get runtime error 6 as soon as I run site swho or !who from my sitebot. If I click ok on the error then the output will process and everything continues to run. But as long as the error is on the screen everything is frozen. Any ideas?

[ADDiCT]

it's about time i add error catching
error 6 = overflow = nevere a good thing to happen

[romracer]

Yea, its almost like it happens when its reading the templates or the ini but I'm not sure. I set the connect time thing it -28800 as that set my login time to zero. Everything else is untouched pretty much from the dZSbot 1.01 release. I even extracted the files through remote desktop instead of uploading them to see if that helped. Same thing. If you want me to test you can find me on irc.

[ADDiCT]

updates in 1.0.8 :
- fixed bug: debug performance counter doesn't cause any error when the api calls fail. I believe it only happens on certain hardware (for example romracer has a dual amd setup).
- fixed bug: overflow could happen on logintime > changed integer (16bit) to long (32bit).
- added error logging to all 'large' functions

Remarks:

• for people who upgrade: only sitewho.exe changed
• upgrade it on your dZSbot as well !

[ADDiCT]

updates in 1.0.9 :
- added option to override default 'site who' command

There is a mistake in the readme.nfo :
replace
who = EXEC ..\scripts\sitewho.exe template=2 override_site_who
with
site = EXEC ..\scripts\sitewho.exe template=2 override_site_who

[odd]

Here comes a stupied question.
You added an option to everride default site who. What does it do? I thought first it would use the templates_limited when doing a site who command so it would be like doing a site xwho, but it didnt work after ive tryed it.

[ADDiCT]

the same as with ioGroups to replace 'site uinfo'

it outputs the info u would normally get from sitewho.exe, and then it blocks ioFTPD's internal 'who' function.