From 1fd21891fde8e97cb91941c32f7e49c4f4881fa7 Mon Sep 17 00:00:00 2001 From: Tom Gilbert Date: Wed, 24 Aug 2005 19:12:14 +0000 Subject: applied patch from ticket #15, and added .inspect to try and work out what exception "reset by peer" gives you. One thing I'm finding troublesome with ruby is working out what exceptions things are going to throw. Especially poorly documented stuff implemented in C. Why the Socket module throws an exception for "reset by peer" which *isn't* a SocketError I don't know, but apparently it does. --- lib/rbot/ircbot.rb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lib/rbot') diff --git a/lib/rbot/ircbot.rb b/lib/rbot/ircbot.rb index 68c2bd47..c30d0e6d 100644 --- a/lib/rbot/ircbot.rb +++ b/lib/rbot/ircbot.rb @@ -116,7 +116,7 @@ class IrcBot @argv = params[:argv] unless FileTest.directory? Config::datadir - puts "data directory '#{Config::datadir}' not found, did you install.rb?" + puts "data directory '#{Config::datadir}' not found, did you setup.rb?" exit 2 end @@ -330,7 +330,7 @@ class IrcBot puts e.backtrace.join("\n") @socket.close # now we reconnect rescue => e # TODO be selective, only grab Network errors - puts "unexpected exception: connection closed: #{e}" + puts "unexpected exception: connection closed: #{e.inspect}" puts e.backtrace.join("\n") exit 2 end -- cgit v1.2.3