software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/001982.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] session limit bug
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20session%20limit%20bug&In-Reply-To=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001981.html">
  11    <LINK REL="Next"  HREF="001986.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] session limit bug</H1>
  15     <B>prince</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20session%20limit%20bug&In-Reply-To="
  17        TITLE="[IRCServices Coding] session limit bug">prince at zirc.org
  18        </A><BR>
  19     <I>Sun Mar 23 21:21:10 PST 2003</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001981.html">[IRCServices Coding] session limit bug
  22 </A></li>
  23         <LI>Next message: <A HREF="001986.html">[IRCServices Coding] session limit bug
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1982">[ date ]</a>
  27               <a href="thread.html#1982">[ thread ]</a>
  28               <a href="subject.html#1982">[ subject ]</a>
  29               <a href="author.html#1982">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>I disagree.  I think it does need a fix.  I do not need to sit and explain
  35 why the command was used, but obviously it's not going to drop at that so I
  36 suppose I must explain a little bit.  I'm not asking all of you people out
  37 there to comment on what I've sent in, but apparently all of you must get in
  38 my business.  I'm asking the coder of this program and list if a fix can be
  39 made or not and if he is willing to do it, not all of you.
  40 If you'd like to know why the command was used I suggest you log on my
  41 network and find out, we have other custom perl services made which use the
  42 SVSKILL command.  Which creates a problem with this &quot;bug&quot; which none of you
  43 seem to think is a bug.  Now, if you could all kindly stop treating me like
  44 a moron which I'm not I'd kindly stop replying to these pointless emails,
  45 which, are very much rather pointless, but for some odd reason I feel the
  46 need to defend myself.   All I would like is a simple yes or no reply from
  47 andrew church and I'll be on my way. ;)
  48
  49 ----- Original Message -----
  50 From: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">RT.Mail at verizon.net</A>&gt;
  51 To: &quot;IRC Services Coding Mailing List&quot;
  52 &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>&gt;
  53 Sent: Monday, March 24, 2003 12:22 AM
  54 Subject: Re: [IRCServices Coding] session limit bug
  55
  56
  57 It doesn't need a fix, it tells you not to use it. It's supposed to send a
  58 raw command to the ircd thru the services, that's what it
  59 does. If it makes the services not function correctly then you should not be
  60 using it for killing people.
  61
  62 &lt; &gt;On Mon, 24 Mar 2003 00:01:08 -0500, prince wrote:
  63 &lt; &gt; Right, it does not say &quot;This command will cause multiple session
  64 &lt; &gt; limits if
  65 &lt; &gt; you use SVSKILL on a user&quot; - and I very much do know what I'm
  66 &lt; &gt; doing.  I
  67 &lt; &gt; think, perhaps, instead of commenting on people's messages you
  68 &lt; &gt; should let
  69 &lt; &gt; somebody who runs this list do so, instead of filling people's
  70 &lt; &gt; inbox up with
  71 &lt; &gt; your pointless ramblings.  I rarely use this list, except when I
  72 &lt; &gt; find
  73 &lt; &gt; something wrong.  I wasn't asking for your comments, I was
  74 &lt; &gt; asking if a fix
  75 &lt; &gt; could be made, I guess you missed that part, eh?  But I'm not
  76 &lt; &gt; here to bicker
  77 &lt; &gt; back and forth with you, my question still stands - can a fix be
  78 &lt; &gt; made?
  79 &lt; &gt; So, Trevor Talbot, don't reply to this, as I'm not insterested
  80 &lt; &gt; in reading
  81 &lt; &gt; what you have to say, yet I'm interested in knowing if it can be
  82 &lt; &gt; fixed.  So
  83 &lt; &gt; please refrain from your comments that do not fix or help this
  84 &lt; &gt; problem in
  85 &lt; &gt; any way. ;)
  86 &lt; &gt;
  87 &lt; &gt; ----- Original Message -----
  88 &lt; &gt; From: &quot;Trevor Talbot&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">quension at mac.com</A>&gt;
  89 &lt; &gt; To: &quot;IRC Services Coding Mailing List&quot;
  90 &lt; &gt; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>&gt;
  91 &lt; &gt; Sent: Monday, March 24, 2003 12:03 AM
  92 &lt; &gt; Subject: Re: [IRCServices Coding] session limit bug
  93 &lt; &gt;
  94 &lt; &gt;
  95 &lt; &gt; &gt; On Sunday, Mar 23, 2003, at 20:41 US/Pacific, prince wrote:
  96 &lt; &gt; &gt;
  97 &lt; &gt; &gt; &gt; Well, I hate to break it to you...but OS help mentions *
  98 &lt; &gt; nothing* of
  99 &lt; &gt; &gt; &gt; this,
 100 &lt; &gt; &gt; &gt; and when I read the fine manual, or fucking manual, however
 101 &lt; &gt; you want
 102 &lt; &gt; &gt; &gt; to put
 103 &lt; &gt; &gt; &gt; it, it also said nothing of this.  So I felt like I should
 104 &lt; &gt; report it.
 105 &lt; &gt; &gt; &gt; If
 106 &lt; &gt; &gt;
 107 &lt; &gt; &gt; It says, &quot;This command has a very limited range of uses, and
 108 &lt; &gt; can wreak
 109 &lt; &gt; &gt; havoc on a network or cause Services to crash if used
 110 &lt; &gt; improperly.  DO
 111 &lt; &gt; &gt; NOT
 112 &lt; &gt; &gt; USE THIS COMMAND unless you are absolutely certain you know
 113 &lt; &gt; what you are
 114 &lt; &gt; &gt; doing!&quot;
 115 &lt; &gt; &gt;
 116 &lt; &gt; &gt; The reason why you are experiencing the issue you are is
 117 &lt; &gt; related to the
 118 &lt; &gt; &gt; ircd's handling of SVSKILL.  ircservices does not do any
 119 &lt; &gt; processing on
 120 &lt; &gt; &gt; the operserv raw command itself; it simply sends it to its
 121 &lt; &gt; uplink
 122 &lt; &gt; &gt; server.
 123 &lt; &gt; &gt; Therefore, if the ircd does not tell services that the user is
 124 &lt; &gt; gone,
 125 &lt; &gt; &gt; services never knows.
 126 &lt; &gt; &gt;
 127 &lt; &gt; &gt; To put it bluntly, you do not know what you are doing.
 128 &lt; &gt; &gt;
 129 &lt; &gt; &gt; &gt; you have a problem with such &quot;lame emails&quot; or &quot;lame
 130 &lt; &gt; comments&quot; about
 131 &lt; &gt; &gt; &gt; IRCServices, perhaps you should remove yourself from the
 132 &lt; &gt; mailing list
 133 &lt; &gt; &gt; &gt; or
 134 &lt; &gt; &gt; &gt; stop replying with comments such as yours? heh.
 135 &lt; &gt; &gt;
 136 &lt; &gt; &gt; That is not my problem.  I replied bluntly and simply because
 137 &lt; &gt; this issue
 138 &lt; &gt; &gt; has been answered several times before.  Mailing list archives
 139 &lt; &gt; exist and
 140 &lt; &gt; &gt; are searchable.
 141 &lt; &gt; &gt;
 142 &lt; &gt; &gt; Even if not understanding the manual/help text completely, a
 143 &lt; &gt; bit of
 144 &lt; &gt; &gt; effort on your part could have avoided this entire email
 145 &lt; &gt; exchange.
 146 &lt; &gt; &gt;
 147 &lt; &gt; &gt; &gt; ----- Original Message -----
 148 &lt; &gt; &gt; &gt; From: &quot;Trevor Talbot&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">quension at mac.com</A>&gt;
 149 &lt; &gt; &gt; &gt;
 150 &lt; &gt; &gt; &gt;&gt; On Sunday, Mar 23, 2003, at 20:13 US/Pacific, prince wrote:
 151 &lt; &gt; &gt; &gt;&gt;
 152 &lt; &gt; &gt; &gt;&gt;&gt; I've found a bug.  Hoooray!
 153 &lt; &gt; &gt; &gt;&gt;
 154 &lt; &gt; &gt; &gt;&gt; No, you haven't.
 155 &lt; &gt; &gt; &gt;&gt;
 156 &lt; &gt; &gt; &gt;&gt;&gt; When you use /msg OperServ raw svskill nickname :reason
 157 &lt; &gt; &gt; &gt;&gt;
 158 &lt; &gt; &gt; &gt;&gt; RTFM, or hell, even just /msg operserv help raw.
 159 &lt; &gt; &gt;
 160 &lt; &gt; &gt; -- Quension
 161 &lt; &gt; &gt;
 162 &lt; &gt; &gt; ---------------------------------------------------------------
 163 &lt; &gt; ---
 164 &lt; &gt; &gt; To unsubscribe or change your subscription options, visit:
 165 &lt; &gt; &gt; <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-">http://www.ircservices.za.net/mailman/listinfo/ircservices-</A>
 166 &lt; &gt; coding
 167 &lt; &gt; &gt;
 168 &lt; &gt;
 169 &lt; &gt; -----------------------------------------------------------------
 170 &lt; &gt; -
 171 &lt; &gt; To unsubscribe or change your subscription options, visit:
 172 &lt; &gt; <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
 173
 174
 175
 176 ------------------------------------------------------------------
 177 To unsubscribe or change your subscription options, visit:
 178 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
 179
 180 </PRE>
 181
 182 <!--endarticle-->
 183     <HR>
 184     <P><UL>
 185         <!--threads-->
 186         <LI>Previous message: <A HREF="001981.html">[IRCServices Coding] session limit bug
 187 </A></li>
 188         <LI>Next message: <A HREF="001986.html">[IRCServices Coding] session limit bug
 189 </A></li>
 190          <LI> <B>Messages sorted by:</B>
 191               <a href="date.html#1982">[ date ]</a>
 192               <a href="thread.html#1982">[ thread ]</a>
 193               <a href="subject.html#1982">[ subject ]</a>
 194               <a href="author.html#1982">[ author ]</a>
 195          </LI>
 196        </UL>
 197
 198 </body></html>