[squid-users] Re: authenticate_program bombs out

Thanks Henrik,

> > i'd thought about that, but i want to also use the log data to manage a
> > 'download quota' system so it really needs to be kept reasonably up to
date.
>
> A log tail daemon keeps the SQL data up to date. There might be a
> seconds gap or so, but not much more if the SQL server can keep up...

cool!

> > > b) Logging to a pipe where another daemon listens, completely avoiding
> > > touching disk.
> >
> > now *that* sounds interesting - any ideas where i might be able to get
some
> > further info on how to do that?
>
> Personally I prefer the log-tail approach, but in UNIX you do this by
>
> mknod p /path/to/log/file
> sql_logger </path/to/log/file
>
> How to do something like this on WIN32 I have no idea.

to me it looks looks simpler to get properly into unix (and variants) - just
one of those things i've been meaning to do but never gotten around to it.

mind you, work that i *have* done with *nix (linix and AIX mostly) have
always been pleasantly appealing ;-) but then again, just about anything's
a fresh change from big-fat MS overkill <sigh>.

> > umm, so are you suggesting that the log daemon can read the log file
even
> > while sqid is writing to it? i am not at all familiar with how that
could
> > be achieved - could you point me to some resources?
>
> Quite simple. The log-tail daemon opens the log and then watches the
> filesize of it, reading data when the file has grown. (actually, it is
> sufficient to just read until EOF, sleep a little and then retry).
>
> The UNIX command tail is one tool for doing this:
>
> tail +0f /path/to/log/file | sql_logger

OK! i'm gonna get cracking on that as soon as i get a chance.

wow i feel like i just discovered lazarus reef! ;-)

thanks again,

regards, Mike.
Received on Tue Mar 27 2001 - 06:45:37 MST