[JDEV] Karma settings

Keith Minkler kminkler at jabber.com
Thu Mar 15 10:29:21 CST 2001

You can put <karma/> sections into each of the c2s and s2s sections, to set specific karma settings,
while still keeping the <karma/> section in your <io/> configuration.  the settings in c2s and s2s will
override those in your <io/> section (you only need to include the tags you wish to override).

(NOTE: This works, but hasn't been fully tested, there may be some karma settings, such as <heartbeat/> 
that will not be overridden, since it is a global setting, therefore only allowed in <io/> -- feedback
as to any problems you encounter would be greatly appreciated)

as to the logging, Last I knew, it called log_notice() when a user ran over thier karma limit, with
a message like "socket from is out of karma"  (jabberd/mio.c 681). The IP address is about
the only information that MIO knows internally, since it has no knowledge of what the socket is being
used for (it could be base_accept/connect, s2s, c2s, transports, etc..) it cannot pull information about
*who* the user is, only what IP address the discrepency came from.

Hope this helps!

On Thu, Mar 15, 2001 at 12:54:09AM -0800, Robert Temple wrote:
> Is it possible to setup karma values per service side component?  From what
> I've read and seen, it looks like there are only two sets of karma settings,
> s2s and c2s.  Can I have custom karma settings for an individual s2s
> component?
> I'd like to know if a connection has been limited by karma, is there an
> entry in the server log file if the server throttled a connection for going
> over its karma?
> Thanks,
> Robert
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
Keith Minkler

Software Developer
Jabber.COM, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20010315/e7b56066/attachment-0002.pgp>

More information about the JDev mailing list