2010/6/26 David Baelde <[email protected]>
> Hi guys,
>
> It is possible to use custom authentication functions, which could be
> useful here: write a function that, when asked too often, says no all
> the time for a while. But this will still not be a very lightweight
> mechanism, perhaps not enough to avoid flood attacks. If fail2ban does
> not work easily, then we should do our best in liquidsoap to avoid
> such problems.
>
> Regarding syslog, I'm happily surprised to see more people interested.
> But help us design it: do you necessarily want labels (INFO, WARN,
> etc) or would you be happy with the current all-INFO patch? How to
> distinguish different liquidsoap instances: PID, name of the script?
>
>
Cool
As I can see in the log of Solvik there is no the real IP of the client
also.
For the lisquidsoap instnace it would be nice to have the PID (easy to
shutdown if a problem appears with kill) but also the name of the script so
it will be really easy to build a munin script for example to monitore all
the instances)
fail2ban is easily scriptable if the logs are quite common with the infos we
need such like IP and so on
that's my poor ideas ...
kent1
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
