[IRCServices Coding] session limit bug

[RT.Mail at verizon.net]

It doesn't need a fix, it tells you not to use it. It's supposed to send a raw command to the ircd thru the services, that's what it 
does. If it makes the services not function correctly then you should not be using it for killing people.

< >On Mon, 24 Mar 2003 00:01:08 -0500, prince wrote:
< > Right, it does not say "This command will cause multiple session
< > limits if
< > you use SVSKILL on a user" - and I very much do know what I'm
< > doing.  I
< > think, perhaps, instead of commenting on people's messages you
< > should let
< > somebody who runs this list do so, instead of filling people's
< > inbox up with
< > your pointless ramblings.  I rarely use this list, except when I
< > find
< > something wrong.  I wasn't asking for your comments, I was
< > asking if a fix
< > could be made, I guess you missed that part, eh?  But I'm not
< > here to bicker
< > back and forth with you, my question still stands - can a fix be
< > made?
< > So, Trevor Talbot, don't reply to this, as I'm not insterested
< > in reading
< > what you have to say, yet I'm interested in knowing if it can be
< > fixed.  So
< > please refrain from your comments that do not fix or help this
< > problem in
< > any way. ;)
< > 
< > ----- Original Message -----
< > From: "Trevor Talbot" <quension at mac.com>
< > To: "IRC Services Coding Mailing List"
< > <ircservices-coding at ircservices.za.net>
< > Sent: Monday, March 24, 2003 12:03 AM
< > Subject: Re: [IRCServices Coding] session limit bug
< > 
< > 
< > > On Sunday, Mar 23, 2003, at 20:41 US/Pacific, prince wrote:
< > >
< > > > Well, I hate to break it to you...but OS help mentions *
< > nothing* of
< > > > this,
< > > > and when I read the fine manual, or fucking manual, however
< > you want
< > > > to put
< > > > it, it also said nothing of this.  So I felt like I should
< > report it.
< > > > If
< > >
< > > It says, "This command has a very limited range of uses, and
< > can wreak
< > > havoc on a network or cause Services to crash if used
< > improperly.  DO
< > > NOT
< > > USE THIS COMMAND unless you are absolutely certain you know
< > what you are
< > > doing!"
< > >
< > > The reason why you are experiencing the issue you are is
< > related to the
< > > ircd's handling of SVSKILL.  ircservices does not do any
< > processing on
< > > the operserv raw command itself; it simply sends it to its
< > uplink
< > > server.
< > > Therefore, if the ircd does not tell services that the user is
< > gone,
< > > services never knows.
< > >
< > > To put it bluntly, you do not know what you are doing.
< > >
< > > > you have a problem with such "lame emails" or "lame
< > comments" about
< > > > IRCServices, perhaps you should remove yourself from the
< > mailing list
< > > > or
< > > > stop replying with comments such as yours? heh.
< > >
< > > That is not my problem.  I replied bluntly and simply because
< > this issue
< > > has been answered several times before.  Mailing list archives
< > exist and
< > > are searchable.
< > >
< > > Even if not understanding the manual/help text completely, a
< > bit of
< > > effort on your part could have avoided this entire email
< > exchange.
< > >
< > > > ----- Original Message -----
< > > > From: "Trevor Talbot" <quension at mac.com>
< > > >
< > > >> On Sunday, Mar 23, 2003, at 20:13 US/Pacific, prince wrote:
< > > >>
< > > >>> I've found a bug.  Hoooray!
< > > >>
< > > >> No, you haven't.
< > > >>
< > > >>> When you use /msg OperServ raw svskill nickname :reason
< > > >>
< > > >> RTFM, or hell, even just /msg operserv help raw.
< > >
< > > -- Quension
< > >
< > > ---------------------------------------------------------------
< > ---
< > > To unsubscribe or change your subscription options, visit:
< > > http://www.ircservices.za.net/mailman/listinfo/ircservices-
< > coding
< > >
< > 
< > -----------------------------------------------------------------
< > -
< > To unsubscribe or change your subscription options, visit:
< > http://www.ircservices.za.net/mailman/listinfo/ircservices-coding