Stephen,
I think it is interesting to use analog for MSPROXY logfiles, oll though I
am still confused about what the proper
LOGFORMAT should be for the optimum use at the moment with the current
analog.......
It seems that analog makes assumptions about the domain and host fields...
The interesting thing is that MSPROXY
logs are mainly ( in my case) interesting for OUTGOING traffic, whereas
analog is more focussed on the incoming
traffic..
The MSPROXY logs, (and I assume also wingate logs and others) contain a lot
of interesting data, like how much data
was actually fetched from the INET and how much data was in the local
cache, which pages changed since the last time
it was cached etc etc.. (If you want to get an idea, you can download
WEBTRENDS for PROXY and use it for free)
I am starting to learn more about analog and the PROXY logs behaviour and
it sound like an applicable and interesting
project for analog......
Any more opinions ANYBODY ???
Erick
> -----Original Message-----
> From: pcrmail [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 05, 2000 11:03 AM
> To: [EMAIL PROTECTED]
> Cc: Erick Otto
> Subject: FW: [analog-help] CODING FOR MSPROXY... (including Winsock
> error code etc etc)
>
>
>
>
> -----Original Message-----
> From: Erick Otto [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 04, 2000 7:37 PM
> To: [EMAIL PROTECTED]
> Subject: FW: [analog-help] CODING FOR MSPROXY... (including Winsock
> error code etc etc)
>
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen Turner
> Sent: Tuesday, January 04, 2000 5:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [analog-help] CODING FOR MSPROXY... (including Winsock
> error code etc etc)
>
>
> On Mon, 3 Jan 2000, Erick Otto wrote:
>
> > 1) How many of you would be interested in this, ie having analog
> recognize
> > MSPROXY codes (maybe later Wingate)
> >
> > 2) I need some help and pointers from stephen about
> where to start
> looking
> > in the code and maybe a little
> > a little code flow help so I can better understand
> the ins and out of
> > analog.
> > (I have been analyzing C-code for years, but it is
> still a major
> effort
> > reading other peoples code)
> >
>
> Well, you have to do two things. First you need a new type of
> input item,
> which accepts codes up to five digits. Then you need to
> assign each new code
> to be a success or failure. (I guess they will mostly, perhaps all, be
> failures).
>
> The second thing happens in process.c from line 194.
>
> The first is a bit more complicated. You need to have a new
> function like
> parsecode() but you also need to parse LOGFORMATs with this
> new item in. I
> can perhaps help you with this if there's enough demand.
>
> --
> Stephen Turner [EMAIL PROTECTED]
> http://www.statslab.cam.ac.uk/~sret1/
> Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
> "Children from St Lawrence's School have buried a time
> capsule to mark
> both
> the millennium and National Tree Week." Cambridge Town
> Crier, 16/12/99
>
> --------------------------------------------------------------
> ----------
> This is the analog-help mailing list. To unsubscribe from this
> mailing list, send mail to [EMAIL PROTECTED]
> with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
> List archived at
> http://www.mail-archive.com/[email protected]/
> --------------------------------------------------------------
> ----------
>
>
>
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
