[IRCServices] Problems With TimeStamping On Bahamut-1.4.23

[Yusuf Iskenderoglu]

Hello;

That means, you suggest services to record the servicesstamp field
for every online nickinfo structure to the database, and check it
against the online nicks servicesstamp, before setting the servicestamp
again.

The feature called servicestamps help ircservices to recover a user
after a netjoin. It is NOT designed to make users identified to
services after services is restarted. The only usage is:

you identify -> your server splits -> your server reconnects ->
you are still identified.

Services shall not save servicestamps into the database.
What if a user is totally new ? Its non existant servicestamp of 0
will be equal to the previous one of 0 (because nothing existed before)
so a user will be identified due to matching services stamps with 
a value of 0.

Additionally, servicestamps do not have anything to do with timestamps.
Timestamp values define the signon time, and have nothing directly to
do with services.

Regards;
yusuf

----------------------------------------------------------------------
| Yusuf Iskenderoglu                | You get to meet all sorts,     |
| eMail - uhc0 at rz.uni-karlsruhe.de  | in this line of work...        |
| eMail - s_iskend at ira.uka.de       |                                |
| ICQ UIN : 20587464 \ TimeMr14C    |                                |
----------------------------------------------------------------------

  
-----Original Message-----
From: ircservices-admin at ircservices.za.net
[mailto:ircservices-admin at ircservices.za.net] On Behalf Of Kevc978
Sent: Samstag, 26. Mai 2001 21:07
To: ircservices at ircservices.za.net
Subject: [IRCServices] Problems With TimeStamping On Bahamut-1.4.23


Hi,

As i believe how services timestamping works, is that if services go
down, for say, an upgrade, when they come back a few minutes later, they
shouldnt ask for a password, I run Bahamut-1.4.23 and i Always upgrade
to the ircservices latest versions, But when services come back,
ChanServ deops all Ops in the channels, and asks you to re-identify, ive
got all the timestamping stuff in services.conf #define'd So, either
this is broken for me, or Ive got the whole Timestamping idea wrong, but
if this is not coded in, its maybe something to think about, as users
dont want to re-identify or have to get ops again in the channel, and i
end up getting all the complaints and arguements.



Kevc978
NetWork Founder
Irc.DarkServ.Net