Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Akill expiry time Anope Anope-1.7.13  (Read 7767 times)

0 Members and 1 Guest are viewing this topic.

RubberDuck

  • Guest
Akill expiry time Anope Anope-1.7.13
« on: February 05, 2006, 03:22:09 PM »

When I set akills with operserv, they dont expire after the time i set. When i do an /operserv akill view, it says "Expires after next database update". I have set "UpdateTimeout" in the conf to the default 5 mins, but the akills seem to expire at random times.

Its on a network of 50+ users, running Unreal3.2.3.

Any ideas?
Logged

TRAiNER4

  • Guest
(No subject)
« Reply #1 on: February 05, 2006, 03:45:34 PM »

Are you sure your servers are synched correctly? When servers link, they have specific TS times, and if they aren't synched, they produce a warning such as this:

[10:43:51a] *** NOTICE:  (sync) Possible negative TS split at link DarkThunder.jtmal.be (1139154188 - 1139154209 = -21) [PLEASE SYNC YOUR CLOCKS!]

if you do get an error like so, make sure your times are set correctly. That is the only thing that comes to my mind.
Logged

Pieter Bootsma

  • Team
  • *
  • Offline Offline
  • Posts: 189
    • http://geniusdex.net/
(No subject)
« Reply #2 on: February 05, 2006, 03:49:49 PM »

If those 'random times' are no longer than 5 minutes it works.
Logged

RubberDuck

  • Guest
(No subject)
« Reply #3 on: February 05, 2006, 04:44:40 PM »

No the times (during my tests) range from 10 to 20 minutes.

Here's an example to illustrate my point:

[18:01]  *** Global -- from OperServ: RubberDuck added an AKILL for blah@thingy ([RubberDuck] Test) (expires in 10 minutes)

After /operserv akill view:
[18:19] -OperServ-   1  blah@thingy (by RubberDuck on Feb 05 2006; expires at next database update)

[18:34] -symmetry.theforesters.net- *** Global -- from OperServ: AKILL on blah@thingy has expired
Logged

Dave Robson

  • Team
  • *
  • Offline Offline
  • Posts: 357
(No subject)
« Reply #4 on: February 06, 2006, 07:29:36 AM »

Is there alot of "traffic" on the network while your doing these tests? bascailly what happens is... anope sits and waits for traffic, when it gets some, it checks if any timers need to be executed, if they do, it does them, deals with the traffic, and then returns to waiting for traffic.   In the event your the only user on the network, there is a strong chance very little traffic is actaully being sent to services, as such, the timers are not accurate.   You can test if this is the case by simply doing a /msg nickserv help every few seconds and see if it improves the accuracy of the timers.
Logged

Cihan

  • Guest
(No subject)
« Reply #5 on: August 03, 2006, 07:56:21 PM »

i am living the same problem. how can we resolve it?
Logged

Pieter Bootsma

  • Team
  • *
  • Offline Offline
  • Posts: 189
    • http://geniusdex.net/
(No subject)
« Reply #6 on: August 04, 2006, 09:44:37 AM »

Isn't this handled with the ExpireTimeout instead of the UpdateTimeout? I haven't checked the code, so i'm not not sure, but it'd explain things (ExpireTimeout defaults to 30 minutes).
Logged

Cihan

  • Guest
(No subject)
« Reply #7 on: August 04, 2006, 10:20:12 AM »

can we set it manually?

if yes. please tell how can we fix it?
Logged

Pieter Bootsma

  • Team
  • *
  • Offline Offline
  • Posts: 189
    • http://geniusdex.net/
(No subject)
« Reply #8 on: August 05, 2006, 08:41:33 AM »

ExpireTimeout is also an option in services.conf
Logged
Pages: [1]   Go Up