software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001657.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 (LONG)
   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%20%28LONG%29&In-Reply-To=3ab54498.42233%40prima-lan.net">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001639.html">
  11    <LINK REL="Next"  HREF="001673.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] A discussion on the contents of the todo file (LONG)</H1>
  15     <B>Mark Hetherington</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20discussion%20on%20the%20contents%20of%20the%20todo%20file%20%28LONG%29&In-Reply-To=3ab54498.42233%40prima-lan.net"
  17        TITLE="[IRCServices] A discussion on the contents of the todo file (LONG)">markh at eurodltd.co.uk
  18        </A><BR>
  19     <I>Tue Mar 20 19:29:05 PST 2001</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001639.html">[IRCServices] A discussion on the contents of the todo file (LONG)
  22 </A></li>
  23         <LI>Next message: <A HREF="001673.html">[IRCServices] A discussion on the contents of the todo file (LONG)
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1657">[ date ]</a>
  27               <a href="thread.html#1657">[ thread ]</a>
  28               <a href="subject.html#1657">[ subject ]</a>
  29               <a href="author.html#1657">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>&gt;<i> &gt;&gt; CS Last used time for access, AKICK entries
  35 </I>&gt;<i> &gt;
  36 </I>&gt;<i> &gt;This is a good idea. This was even mentioned by someone recently.
  37 </I>&gt;<i> &gt;So lets discuss it and see how many people like it.
  38 </I>&gt;<i>
  39 </I>&gt;<i>      I'm already planning to implement this in 5.0 unless there's some
  40 </I>&gt;<i> objection.
  41 </I>
  42 Not sure what the exact plan is but I think it would be very useful to
  43 extend this feature a little further. Add a field to the access and akick
  44 lists which stores the date/time and nickname of the person performing an
  45 operation on the lists. So the AOP/AKICK etc lists would become e.g.
  46 (nickname) (level) (added/changed on) (added/changed by). Basically a
  47 similar setup to the AKILL list.
  48
  49 &gt;<i> &gt;&gt; ** Services log channel
  50 </I>&gt;<i> &gt;Was there a recent discussion on this?
  51 </I>&gt;<i>
  52 </I>&gt;<i>      Not recent, but a long time ago there was some discussion about
  53 </I>&gt;<i> this.  As I recall, it essentially came down to the benefit of being
  54 </I>&gt;<i> able to monitor the log online (remotely) vs. the security problems of
  55 </I>&gt;<i> having Services status information broadcast on the network and the
  56 </I>&gt;<i> additional network load.  I personally think it would be better off
  57 </I>&gt;<i> not being added, but I'm open to comments.
  58 </I>
  59 One of our statistics psuedo clients echos a lot of network information to a
  60 channel and by use of the Oper only channel mode, we limit who can access
  61 the information. It is often useful to have all this information online. As
  62 with many things, implementation could be an option in the configuration
  63 (ala StatServ) so anyone concerned about load and security could not run it
  64 at all. I see that it could be a *very* useful debugging tool to have online
  65 echoing from services. If it were implemented, I would like to be able to
  66 configure what it will echo to channel. Some information would not always be
  67 necessary.
  68
  69 The discussion on a new logging format suggests that being able to &quot;tune&quot;
  70 the information logged would be trivial to implement both for any channel
  71 echo and the actual log itself during the rewrite of the logging code.
  72
  73 Mark.
  74 CTCP Networks.
  75
  76
  77
  78 </PRE>
  79
  80 <!--endarticle-->
  81     <HR>
  82     <P><UL>
  83         <!--threads-->
  84         <LI>Previous message: <A HREF="001639.html">[IRCServices] A discussion on the contents of the todo file (LONG)
  85 </A></li>
  86         <LI>Next message: <A HREF="001673.html">[IRCServices] A discussion on the contents of the todo file (LONG)
  87 </A></li>
  88          <LI> <B>Messages sorted by:</B>
  89               <a href="date.html#1657">[ date ]</a>
  90               <a href="thread.html#1657">[ thread ]</a>
  91               <a href="subject.html#1657">[ subject ]</a>
  92               <a href="author.html#1657">[ author ]</a>
  93          </LI>
  94        </UL>
  95
  96 </body></html>