Got rid of some debugging code we tried to use to track the 100% CPU bug.

Turned out it was very suitable DoS code. :-)

1 files changed, 0 insertions, 6 deletions

diff --git a/bitlbee.c b/bitlbee.c
index 66552130..e32b0e90 100644
--- a/bitlbee.c
+++ b/bitlbee.c
@@ -40,8 +40,6 @@ gboolean bitlbee_io_new_client( GIOChannel *source, GIOCondition condition, gpoi
 	int new_socket = accept( global.listen_socket, (struct sockaddr *) &conn_info, 
 		                     &size );
 	
-	count_io_event(source, "main");
-	
 	log_message( LOGLVL_INFO, "Creating new connection with fd %d.", new_socket );
 	irc_new( new_socket );
 
@@ -124,8 +122,6 @@ gboolean bitlbee_io_current_client_read( GIOChannel *source, GIOCondition condit
 	char line[513];
 	int st;
 	
-	count_io_event(source, "main");
-
 	if( condition & G_IO_ERR || condition & G_IO_HUP )
 	{
 		irc_free( irc );
@@ -181,8 +177,6 @@ gboolean bitlbee_io_current_client_write( GIOChannel *source, GIOCondition condi
 	time_t newtime;
 #endif
 
-	count_io_event(source, "main");
-
 #ifdef FLOOD_SEND	
 	newtime = time( NULL );
 	if( ( newtime - irc->oldtime ) > FLOOD_SEND_INTERVAL )