[WRT to this list, I think it'd be great to have it online, searchable, etc.,
so newcomers or lurkers can see what's up here. (Or I just want to look
something up myself and can't find/lose my mail archive). Can anyone do
this, or is there any problem with this?]
Now...
[...sorry, not sure who said this...]
> Last call: has ANYONE had contact with Lucio Torre from Buenos Aires, or
> been able to download and test his work?? If not, I suggest we drop his
> work from the discussion, because there is just not enough information
> available.
I can get that one, but I haven't been able to get darren's. But do we
want to talk implementations or requirements first? Seems to me the way
to go about it is requirements, design, and then implementations, myself.
Working for an ISP (earthlink) that has enormous amounts of traffic and
volume I'm concerned about performance & scalability as well as the usual
issues... but what are the usual issues? I'd like something like (tossing
out the straw girl/boy):
o easy to use & set up
o central & individual host logging capabilities
o "very hard" (whatever that means) to change or insert records
o "hard" (less difficult than "very hard", I guess ;-)) to log
anything at all by anything but things you want to be logging
o text based log format (readable, grep'able, etc.)
o scales to large networks and vast amounts of traffic
o not tied to any other programs, hardware, etc.
o freely usable (commercial or otherwise) implementation with source
I guess it has to have at least all the functionality of syslog without
too many negatives. Perhaps -
o plug-n-play with various crypto methods
o exportable from the US (presuming crypto is used, I assume it will be)
Does anyone agree with any/all of these? I realize that they may not be
realistic, but for a wish list, this is where I might start. What else do
we want? Feel free to point me to a FM (as in RTFM), etc. I'm not at all
tied to this list, show me a good one.
-- d
