[geeklog-devel] access.log

[Blaine Lang]

I think these are good ideas. As developers we often use COM_errorLOG for
debugging output and I think that is become a problem and often leaves
spurious non-error related outout in that log which can only confuse a user.

I've introduced a notification.log file with glMessenger and maybe we should
have a debug.log file.
The logic would check for the existance of the file and if not there
doNothing() else logEntry().

In my case, I also wrote a small block that I only see so I can tail the
notification log and watch my site activity. During debugging, having a
Centerblock doing a tail on the debug.log file may be handy.

If I knew there was a standard COM_debugLog(), then I'd convert any of my
code to use that.

----- Original Message ----- 
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Sent: Saturday, January 17, 2004 8:14 AM
Subject: Re: [geeklog-devel] access.log


> Vincent wrote:
>
> >Another tangent: In the future, if we kept track of how many failed
> >login attempts since last succesfull login, we could do some pretty cool
> >stuff (like lock and possibly send email to the affected person and
> >admin that a login has failed three times on an account).
>
> Good point. Actually, we probably shouldn't start logging failed login
> attempts until they've exceeded a certain number (say, 3) - everyone
> mistypes their password once in a while ...
>
> Blocking an account after a certain amount of failed login attempts just
> calls for misuse, but sending an email (to the user at least) sounds like
> a good idea.
>
> bye, Dirk
>
>
> -- 
> http://www.haun-online.de/
> http://mypod.de/
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://lists.geeklog.net/listinfo/geeklog-devel