On Tue, 19 Oct 1999, Rob Cermak wrote: > On Tue, 19 Oct 1999, d wrote: > > I thought chris calabrese might mention this (he sent it to me), but > > another nice feature to have would be having regexp support. (Various > > places it could be.) > > Good suggestion. This may not be a problem. Might be a separate > syslog.conf option list to shunt certain messages off to a certain log or > agent? .*denied.* LOGHOST(security.domain.com,tcp,125) Question is, would that be anything of interest for the -protocol-? I was under the impression this list was more into coming up with something workable in that department than the blo^H^H^Hfunctionality of the apps that'll talk said protocol.. For instance, regex matching would be better up to the recieving host/proxy relay host/WAP toy/whatever, I'd think, no? Some way of negotiating the data would be spiffy, speaking of bloat.. if the client side feels like sending its local timestamps in binary, or 'negotiate away' some field or functionality, that certainly wouldnt -hurt-.. Actually, ideal (imo, but I'm a bit weird, so feel free to ignore me) would probably be two protocols - a fat one with content negotiation and whatnot other junk, and a thinner one for dumb clients to use - the thinner dumps data in a very simple and standard format, the fatter one requires the hosts to check data before it sends it further. Scenario: Host A Host B --ethernet-- Host D ----slow connection---- Host E Host C The hosts A-C spews a lot of data to host D (simple protocol, no negotiation). Host E doesnt want any data of type 'lowlevel', but accepts 'problems'. Host B goes low on memory, and something posts this as a problem. Host E can then send a request for host D to start sending 'lowlevel' where the source is host B, and hopefully something can see that something started forking like hell, still without chewing up the slow connection too much by sending junk over it. Not the best of examples, granted, but hopefully, the idea is found under all the words :) Requesting historical data from hosts that support it could also be useful. Net break at 12:50? No sweat, request data from 12:50 up 'til now as soon as it's reachable again. If the host doesnt support it, it doesnt, if it does, more usefulness to you. Kriss Andsten --- .... --..-- -.-- --- ..- .-. . .- -.. -- --- .-. ... . --..-- . .... ..--.. Kriss Andsten <[EMAIL PROTECTED]> telnet slartibartfast.vogon.se 4243
