]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001636.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001636.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] A discussion on the contents of the todo file
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20discussion%20on%20the%20contents%20of%20the%20todo%20file&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="001635.html">
11 <LINK REL="Next" HREF="001640.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] A discussion on the contents of the todo file</H1>
15 <B>Trevor Talbot</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20discussion%20on%20the%20contents%20of%20the%20todo%20file&In-Reply-To="
17 TITLE="[IRCServices] A discussion on the contents of the todo file">quension at softhome.net
18 </A><BR>
19 <I>Mon Mar 19 03:22:01 PST 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001635.html">[IRCServices] A discussion on the contents of the todo file (LONG)
22 </A></li>
23 <LI>Next message: <A HREF="001640.html">[IRCServices] A discussion on the contents of the todo file
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1636">[ date ]</a>
27 <a href="thread.html#1636">[ thread ]</a>
28 <a href="subject.html#1636">[ subject ]</a>
29 <a href="author.html#1636">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Andrew Church wrote:
35
36 &gt;<i> &gt;&gt; ** Services log channel
37 </I>&gt;<i> &gt;Was there a recent discussion on this?
38 </I>&gt;<i>
39 </I>&gt;<i> Not recent, but a long time ago there was some discussion about
40 </I>&gt;<i> this. As I recall, it essentially came down to the benefit of being
41 </I>&gt;<i> able to monitor the log online (remotely) vs. the security problems of
42 </I>&gt;<i> having Services status information broadcast on the network and the
43 </I>&gt;<i> additional network load. I personally think it would be better off
44 </I>&gt;<i> not being added, but I'm open to comments.
45 </I>
46 As a rumor claims, DALnet once had a log channel for their proxy
47 scanners. It became a liability, as people would attempt to ride in on
48 netsplits. Those who managed to stay for awhile logged the proxies,
49 then made good use of them on servers that did not run the scanner (or
50 after attacking the scanner into oblivion).
51
52 While that's unconfirmed, it certainly rings true with human behavior.
53 I'd suggest adding in a hostmask-regulated telnet module or similar (I'd
54 go for DCC, but that wouldn't allow giving commands to OperServ while
55 not on IRC). Along with live log watching, you could have a parser scan
56 the new log files and show you past history on a nick or channel, etc.
57 If thread support is sufficient on the OSes services runs on, such a
58 module would be useful as a separate thread: skips around shell process
59 restrictions, and no lag on services while crunching logs.
60
61 -- Quension
62
63
64 </PRE>
65
66 <!--endarticle-->
67 <HR>
68 <P><UL>
69 <!--threads-->
70 <LI>Previous message: <A HREF="001635.html">[IRCServices] A discussion on the contents of the todo file (LONG)
71 </A></li>
72 <LI>Next message: <A HREF="001640.html">[IRCServices] A discussion on the contents of the todo file
73 </A></li>
74 <LI> <B>Messages sorted by:</B>
75 <a href="date.html#1636">[ date ]</a>
76 <a href="thread.html#1636">[ thread ]</a>
77 <a href="subject.html#1636">[ subject ]</a>
78 <a href="author.html#1636">[ author ]</a>
79 </LI>
80 </UL>
81
82 </body></html>