[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: service design in /TRACE and ircd.conf

To: ircd-users@xxxxxxx
Subject: Re: service design in /TRACE and ircd.conf
From: Christophe Kalt <kalt@xxxxxxxxxxx>
Date: Thu, 18 Feb 1999 20:46:01 -0500
Delivered-to: ircd-users-out@irc.org
Delivered-to: ircd-users@irc.org
In-reply-to: <Pine.NEB.3.96.990217095316.17084A-100000@kip.sateh.com>; from Thomas Kuiper on Wed, Feb 17, 1999 at 09:55:16AM +0100
Mail-followup-to: ircd-users@irc.org
References: <Pine.NEB.3.96.990217095316.17084A-100000@kip.sateh.com>

On Feb 17, Thomas Kuiper wrote:
| Shouldnt TRACE for services show:
| * Service 4711 TkSurf@xxxxxxxxxx[unknown@194.163.252.41] 0x2000000 33619968
| instead of 33554432,

it could..

|                      and is it any way possible to implement a service to
| your ircd.conf using hex values?

I guess this could be changed as well.

I don't feel strongly about it, if anybody does, speak up
now.

Thomas: I won't spend time on this, feel free to submit a
diff to ircd-dev

References:
- service design in /TRACE and ircd.conf
  - From: Thomas Kuiper

Prev by Date: Re: Current PING/PONG implementation to violate the RFC
Next by Date: Re: mode +k
Previous by thread: service design in /TRACE and ircd.conf
Next by thread: 2.10.2p1 files
Index(es):
- Date
- Thread