in reply to Re^7: Perl Alarm Not Working
in thread Perl Alarm Not Working

       C calls are not interruptible

Hmm...?? How do we explain the followings:

I made a demostration delibrately make MySql execute to a Maximum time of 5 sec, then set a timeout alarm of 3 sec in eval{} to prevent MySql execution more than 3 sec.

To my surprise, timeout alarm in eval{} stops MySql execution exactly at 3 sec. COSISTENTLY

The followings is the demonstration script:
#!/usr/bin/perl $max_time = 5; $timeout = 3; use DBI; print "Content-type: text/html\n\n"; sub do_counter { $time1 = time; $time2 = time; $counter = 0; $time_ran = $time2 - $time1; $dbh=DBI->connect("dbi:mysql:$database:localhost","username"," +password"); $query="SELECT name FROM test"; $sth=$dbh->prepare($query); $sth->execute(); while ( @row = $sth->fetchrow_array ) { while($time_ran <= $max_time) { $conter++; $time2 = time; $time_ran = $time2 - $time1; } } $sth->finish; $dbh->disconnect ||die("Couldn't disconnect to database!\n"); } eval { local $SIG{ALRM} = sub { die "alarm\n" }; alarm $timeout; &do_counter; alarm 0; }; if($@) { print "$@, Time Ran: $time_ran, Counter: $conter\n"; exit; } print "Time Ran: $time_ran, Counter: $conter\n"; exit;

As you can see, I delibrately make a counter loop inside MySql's while ( @row = $sth->fetchrow_array ) loop. The counter loop can run to a $max_time of 5 sec. before it stops.

In the eva{} I set a timeout alarm of 3 sec. to stop MySql execution from going over 3 sec.

When I ran the above script, I got the following results consistently:

alarm, Time Ran: 3, Counter: 3341554
alarm, Time Ran: 3, Counter: 3416456

These results show that alarm in eval{} has stopped MySql execution in 3 sec.

Can we not say then that alarm has interrupted MySql C Calls (e.g. calls to the db driver), contrary to what you said?

You can do the same demostration with the above script by doing the followings:

1) Create a table TEST with a single column: name CHAR(30) NOT NULL
2) Enter 3 names, like John, Paul, Mary in the table.
3) Run the above script.

Replies are listed 'Best First'.
Re^9: Perl Alarm Not Working
by ikegami (Patriarch) on Dec 21, 2010 at 17:34 UTC

    Can we not say then that alarm has interrupted MySql C Calls (e.g. calls to the db driver), contrary to what you said?

    No.

    while ( @row = $sth->fetchrow_array ) { while($time_ran <= $max_time) { $conter++; $time2 = time; $time_ran = $time2 - $time1; } }

    isn't C.

Re^9: Perl Alarm Not Working
by Anonymous Monk on Dec 21, 2010 at 12:34 UTC
    Can we not say then that alarm has interrupted MySql C Calls (e.g. calls to the db driver), contrary to what you said?

    No, pay attention , unsafe signals will interrupt c calls. Refer to documentation, its what we do.

      Fine. How can we tell which signals are safe, which signals are unsafe then?