On Dec 8, 2007 9:28 AM, NewbeeUnix <[EMAIL PROTECTED]> wrote: > Yes I did tried with Sybase::DBlib and it works with that.. > I also came to the same conclusion that CTlib is catching it > somehow... > Is there a way to not allow that.... > Also DBlib module cannot be used ... some restrictions are there.... snip
What exactly are you trying to do with Sybase? If all you want to do is run SQL statements against it (the most common case) you are better off with the DBI* and DBD::Sybase** modules. Using the DBI module, a database independent framework, will give you a lot more flexibility if at some later date you change to a different RDBMS vendor (like Oracle, DB2, etc.). Also, why are you concerned with catching SIGHUP? The only reason, in my mind, to catch it is to prevent a process from exiting when the controlling terminal closes (which shouldn't affect a properly created daemon since it wouldn't have a controlling terminal). If Sybase::CTlib is already causing the program to ignore SIGHUP then that is one less thing you need to do. * http://search.cpan.org/dist/DBI/DBI.pm ** http://search.cpan.org/dist/DBD-Sybase/Sybase.pm -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
