@@ -8,24 +8,33 @@ Sys::SigAction::Changes - List of significant changes
 
 Revision history for Sys::SigAction.
 
+=head2 Changes in Sys::SigAction 0.21  20 Nov 2013
+
+Remove erroneous note at the end of the POD related to references to
+this module in DBD:Oracle.  In reality the reference was in DBI, and it
+is still there.
+
+Close pod error bug (which referred to the above paragraph) submitted
+by the Debian Packaging team.
+
 =head2 Changes in Sys::SigAction 0.20  4 Aug 2013
 
 Even if C<Time::HiRes::ualarm()> exists, it may not necessarily
-work. (There were way too many broken smoke tests with were
-the result of this. One reason for this may bave been that the test
-was looking for too small an interval of sub-second timeouts.  On busy 
-systems, this may have been causing tests to fail.
+work. (There were way too many broken smoke tests which might have been
+the result of this). One reason for this may also bave been that the test
+was looking for too small an interval in the sub-second timeout tests.  On busy 
+systems, this may also have been causing tests to fail.
 
-Got rid of the attempt at tracking broken environments in timeout.t 
-(the hash structure mentioned in the previous change.
+This version got rid of the attempt at tracking broken environments in timeout.t 
+(the hash structure mentioned in the previous change).
 
 The sub-second timer tests now set a timeout at 0.1 seconds, and check
-for a delta time the is less then 0.8 seconds. Proving that they completed
-in under 1 second, but give a wide range of execution time to account
-for busy systems.
+for a delta time that is less than 0.8 seconds. Proving that they completed
+in under 1 second. This provides a 0.7 second range of execution time to account
+for busy systems.  Previous tests, only allowed for something less than 0.1 second.
 
-Also Makefile.PL now looks for C<Time::HiRes::ualarm()>, and tests it.
-If it works, high resolution timeouts are enabled in Sys
+Makefile.PL now looks for C<Time::HiRes::ualarm()>, and tests it.
+If it works, high resolution timeouts are enabled.
 Makefile.PL reports what it finds, and t/timeout.t reports when high
 resolution tests are disabled, but timeout.t should not fail because of
 this... it will just run fewer tests.

@@ -1,6 +1,6 @@
 --- #YAML:1.0
 name:               Sys-SigAction
-version:            0.20
+version:            0.21
 abstract:           Perl extension for Consistent Signal Handling
 author:
     - Lincoln A. Baxter <lab-at-lincolnbaxter-dot-com>

@@ -34,7 +34,7 @@ if ( ! $@ || $Config{usethreads} || $Config{useithreads} || $Config{use5005threa
    This perl has multithread support enabled, this is not a problem for
    single threaded perl applications.
    
-   Please see "MULTITHREAD PERL in the Sys::SigAction POD for more information
+   Please see "MULTITHREAD PERL" in the Sys::SigAction POD for more information.
 
    Lincoln
 
@@ -82,14 +82,14 @@ if ( $^O =~ /cygwin/ ) {
    warn q(
    Smoke testers have discovered that t/mask.t fails on at least
    some verions cygwin. Specific versions of the os and perl
-   and now protected... but others may be found. On this platforms
+   are now protected... but others may be found. On these platforms
    masking signals probably does not work. See the hash reference
    \$broken_platforms for platforms known to be broken.
 
    );
 }
 
-my $SAAD = "lib/Sys/SigAction/" ;
+my $SAAD = "lib/Sys/SigAction" ;
 my $SAA = "$SAAD/Alarm.pm" ;
 print "Writing $SAA\n" ;
 mkdir $SAAD if ( not -d $SAAD );
@@ -152,9 +152,10 @@ else {
       $et = Time::HiRes::time();
       #print "outside forever eval\n" ;
    };
+   Time::HiRes::ualarm( 0 );
    my $delta = $et - $st;
    if ( $delta < 0.8 ) {
-      print q( 
+      print qq( 
    Time::HiRes::ualarm() exists and works.
    High resolution timeouts enabled." 
 );
@@ -162,8 +163,8 @@ else {
    }
    else
    {
-      warn q(
-   Time::HiRes exists on this platform but Time::HiRes::ualarm
+      warn qq(
+   Time::HiRes exists on this platform but Time::HiRes::ualarm()
    appears to be broken.  High resolution timeouts disabled.
 );
    }
@@ -173,7 +174,7 @@ close( SAH );
 print "\nWrote $SAA\n" ;
 
 if ( not $hr_works ) {
-   warn q(
+   warn qq(
    Fractional seconds in timeout_call() may be used but will be 
    raised to the next higher integer value with POSIX::ceil().
 );

@@ -29,7 +29,7 @@ sub sig_alarm
 
 @ISA = qw( Exporter );
 @EXPORT_OK = qw( set_sig_handler timeout_call sig_name sig_number sig_alarm );
-$VERSION = '0.20';
+$VERSION = '0.21';
 
 use Config;
 my %signame = ();
@@ -535,8 +535,8 @@ Read the following from perldoc perlthrtut:
 That said, perl documentation for perl threading discusses a a way of
 emulating signals in multi-threaded applications, when safe signals
 is in effect. See perldoc threads and search for THREAD SIGNALLING.
-I have no test of multithreading and this module.  If you thing they
-could used compatibly, and would provide value, patches are welcome.
+I have no test of multithreading and this module.  If you think they
+could be used compatibly and would provide value, patches are welcome.
 
 =head1 AUTHOR
 
@@ -556,11 +556,4 @@ could used compatibly, and would provide value, patches are welcome.
    perldoc perlvar 
    perldoc POSIX
 
-=head NOTE
-
-Recent versions of DBD::Oracle no longer reference this module in the
-POD, so DBD::Oracle may now have solved the connection timeout problem
-internally. For older versions, the dbd-oracle-timeout.pod file provides
-a DBD-Oracle test script, which illustrates the use of this
-module with the DBD-Oracle driver.