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? Cheers, David ------------------------------------------------------------------------------ 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
