[Omaha.pm] FW: DBD::Informix & $SIG{ALRM} & /etc/services

["Jay Hannah" <jhannah@omnihotels.com>]

FYI. In case you care about my Informix $SIG{ALRM} woes. :)

j


-----Original Message-----
From: Jonathan Leffler [mailto:jonathan.leffler@gmail.com] 
Sent: Friday, November 03, 2006 4:30 PM
To: Jay Hannah
Cc: dbi-users@perl.org; Guardian of DBD::Informix
Subject: Re: DBD::Informix & $SIG{ALRM} & /etc/services



On 11/3/06, Jay Hannah <jhannah@omnihotels.com> wrote:


	Oops. I noticed my versions were behind. I upgraded DBI and
DBD::Informix.
	
	I'm still getting the same behavior (14.3 seconds to time out),
so I'm
	still curious about what might be going on.


CSDK probably uses  alarm itself - for connection timeouts, no less - so
your attempt to use alarm at the same time is likely to cause confusion
somewhere.

You could probably track this with the equivalent of truss (strace on
Linux?), looking for alarm system calls in the output.  You'd probably
be able to identify your own alarm(2) call; you might have to work
harder to identify which other alarm() calls are made before you see
SIGALRM fire. 

Interestingly, the manual page for the system call is usually designated
alarm(2) as well as you using an alarm function call with the argument
value 2.



	$ perl -MDBI -e'DBI->installed_versions'
	  Perl            : 5.008004    (i686-linux)
	  OS              : linux       (2.6.4-52-smp)
	  DBI             : 1.53
	  DBD::Sybase     : 1.04
	  DBD::Sponge     : 11.10
	  DBD::Proxy      : install_driver(Proxy) failed: Can't locate
	RPC/PlClient.pm in @INC
	  DBD::Informix   : 2005.02
	  DBD::File       : 0.35
	  DBD::ExampleP   : 11.12
	  DBD::DBM        : 0.03
	
--
Jonathan Leffler <jonathan.leffler@gmail.com>  #include <disclaimer.h>
Guardian of DBD::Informix - v2005.02 - http://dbi.perl.org "I don't
suffer from insanity - I enjoy every minute of it."