]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000829.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2000 / 000829.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Desperate Problems
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Desperate%20Problems&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="000821.html">
11 <LINK REL="Next" HREF="000831.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Desperate Problems</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Desperate%20Problems&In-Reply-To="
17 TITLE="[IRCServices] Desperate Problems">achurch at dragonfire.net
18 </A><BR>
19 <I>Tue Oct 10 23:11:00 PDT 2000</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000821.html">[IRCServices] Desperate Problems
22 </A></li>
23 <LI>Next message: <A HREF="000831.html">[IRCServices] cheers. ideas.
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#829">[ date ]</a>
27 <a href="thread.html#829">[ thread ]</a>
28 <a href="subject.html#829">[ subject ]</a>
29 <a href="author.html#829">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&lt;rant&gt;
35
36 Permit me to offer _my_ years of experience and point out that network
37 and server maintenance is completely meaningless without users. This is
38 just as true of IRC as of the Internet in general; when was the last time
39 you talked to someone maintaining a gopher server, for example? This is
40 what we in the field technically refer to as &quot;being too literal&quot;.
41 Example:
42
43 If you read RFC 1459, scripting isn't even mentioned, whereas the
44 duties of an IRCop are; in such duties are network/server maintenance.
45 So by standard, choosing to keep a network tool like StatServ would be
46 more helpful to the oper than worrying about whether or not a few users
47 get flooded by clonebots.
48
49 (Note that StatServ and {nick protection, scripting} are entirely
50 orthogonal, except to the extent that nick protection and StatServ run in
51 the same process; and of course, if StatServ crashes then StatServ can't
52 continue working as a network tool, which makes this a non-solution to
53 start with.)
54
55 Of course, this is completely irrelevent to the original question,
56 which was not &quot;I'm going to pick one of these two things to get rid of,
57 which one should I choose&quot;. The original question was &quot;Having StatServ
58 enabled causes Services to crash, how can I make it stop crashing?&quot;
59 Saying &quot;Leave StatServ enabled and let the users deal with Services
60 crashing&quot; does not answer that question.
61
62 &lt;/rant&gt;
63
64 --Andrew Church
65 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at dragonfire.net</A>
66 <A HREF="http://achurch.dragonfire.net/">http://achurch.dragonfire.net/</A>
67
68 &gt;<i>I was suggesting a lesser of two evils. Services is in no way required for
69 </I>&gt;<i>network maintenance, so asking me to decide which is more helpful, is
70 </I>&gt;<i>totally irrelevant.
71 </I>&gt;<i>
72 </I>&gt;<i>A good set of opers and a RFC compliant IRCd will have all the tools needed
73 </I>&gt;<i>for the task. Please remember that IRC was conceived without services and
74 </I>&gt;<i>the oldest net still runs without them.
75 </I>&gt;<i>
76 </I>&gt;<i>I'm not one to get into a heated debate over my opinion.
77 </I>&gt;<i>
78 </I>&gt;<i>If you read RFC 1459, services isn't even mentioned. Where as the duties of
79 </I>&gt;<i>an IRCop are, in such duties are network/server maintenance. So by
80 </I>&gt;<i>standard, choosing to keep a network tool like StatServ would be more
81 </I>&gt;<i>helpful to the oper than worrying about whether or not a few nicks get
82 </I>&gt;<i>changed/killed.
83 </I>&gt;<i>
84 </I>&gt;<i>Whatever you decide is of course your choice alone, I'm just here to help
85 </I>&gt;<i>by offering my years of experience.
86 </I>&gt;<i>
87 </I>&gt;<i>I do trust that these problems will be handled in the near future. In the
88 </I>&gt;<i>short time I have known Andrew, he has always been good about fixing
89 </I>&gt;<i>problems in a timely manner.
90 </I>&gt;<i>
91 </I>&gt;<i>&lt;/rant&gt;
92 </I>&gt;<i>
93 </I>&gt;<i>
94 </I>&gt;<i>Scott Seufert
95 </I>&gt;<i>aka katsklaw
96 </I>&gt;<i>Server Admin
97 </I>&gt;<i>Excalibre.ShadowFire.Org
98 </I>&gt;<i>
99 </I>&gt;<i>
100 </I>&gt;<i>&lt;snip&gt;
101 </I>&gt;<i>
102 </I>&gt;&gt;<i> &gt; This creates an inconvenience for the user, but keeps the network
103 </I>&gt;&gt;<i> stable(The
104 </I>&gt;&gt;<i> &gt; IRCop's prime duty, IAW RFC1459).
105 </I>&gt;&gt;<i>
106 </I>&gt;&gt;<i>Umm not having services and having services... u decide which is more
107 </I>&gt;&gt;<i>helpful in keeping the network up and running
108 </I>&gt;&gt;<i>properly. Keep in mind the 22% cpu usage, having to restart services on
109 </I>&gt;&gt;<i>the server, and that guesting will only cause
110 </I>&gt;&gt;<i>confusion, and nothing else. IMHO both should be removed on a temporary
111 </I>&gt;&gt;<i>basis until the issues are resolved.
112 </I>&gt;&gt;<i>
113 </I>&gt;&gt;<i> &gt; Scott Seufert
114 </I>&gt;&gt;<i> &gt; aka katsklaw
115 </I>&gt;&gt;<i> &gt; Server Admin
116 </I>&gt;&gt;<i> &gt; Excalibre.ShadowFire.Org
117 </I>&gt;&gt;<i>
118 </I>&gt;&gt;<i>Imran Ali Rashid
119 </I>&gt;&gt;<i>Server Admin of a small tiny, two servers linked across a modem irc
120 </I>&gt;&gt;<i>network. Converting the modem link to lan in about a
121 </I>&gt;&gt;<i>week, so splits issue should be non-existant.
122 </I>&gt;&gt;<i>irc.giki.edu.pk
123 </I>&gt;&gt;<i>
124 </I>&gt;&gt;<i>
125 </I>&gt;&gt;<i>---------------------------------------------------------------
126 </I>&gt;&gt;<i>To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
127 </I>&gt;&gt;<i>with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
128 </I>&gt;<i>
129 </I>&gt;<i>
130 </I>&gt;<i>---------------------------------------------------------------
131 </I>&gt;<i>To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
132 </I>&gt;<i>with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
133 </I>
134 ---------------------------------------------------------------
135 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
136 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
137
138
139 </PRE>
140
141 <!--endarticle-->
142 <HR>
143 <P><UL>
144 <!--threads-->
145 <LI>Previous message: <A HREF="000821.html">[IRCServices] Desperate Problems
146 </A></li>
147 <LI>Next message: <A HREF="000831.html">[IRCServices] cheers. ideas.
148 </A></li>
149 <LI> <B>Messages sorted by:</B>
150 <a href="date.html#829">[ date ]</a>
151 <a href="thread.html#829">[ thread ]</a>
152 <a href="subject.html#829">[ subject ]</a>
153 <a href="author.html#829">[ author ]</a>
154 </LI>
155 </UL>
156
157 </body></html>