Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Hard coded exceptions in services.conf  (Read 5242 times)

0 Members and 1 Guest are viewing this topic.

dev_

  • Guest
Hard coded exceptions in services.conf
« on: February 16, 2006, 09:51:04 AM »

Hello
First of all I would like to thank everyone for a great irc service which as served me well over many years. Second of all, I would like to suggest a feature. It's may not be vital, and it probably isn't very hard to do.

Would it be possible to add "hard coded" exceptions in services.conf? Simply add IPs/Hostnames and session limits that doesn't expire or depend on the .db.

This would be handy for us using (for example) cgi:irc which acts like a proxy. Now I must add an exception that doesn't expire for 999d and 1000 users everytime I add a webbserver or change my hostname, otherwise anope will (as programmed) go to war on it, so to speak.

Regards,
Niklas
Logged

Dave Robson

  • Team
  • *
  • Offline Offline
  • Posts: 357
(No subject)
« Reply #1 on: February 16, 2006, 11:55:56 AM »

Add the timeout as 0 which never expires.  Regarding the changing of the hostname - wouldnt you have to do that anyway with a .conf setting?
Logged

dev_

  • Guest
(No subject)
« Reply #2 on: February 16, 2006, 12:20:59 PM »

You are quite right, didn't know about timeout 0. Thank you for your fast reply and answer.

Regards,
Niklas

[Edited on 16-2-2006 by dev_]
Logged
Pages: [1]   Go Up