in reply to Re^4: DBI messes up sleep
in thread DBI messes up sleep

Since other users where able to reproduce it and provide work around its sounded good. At least it should be addressed as a comment in the documentation so that if someone else has the same problem they will be able to find a solution sooner. Either way I don't think submitting it as a bug is hasty because the maintaners may have no idea of the issue and might not read PM, if that is the case then some kind of notification to them would be good.


___________
Eric Hodges

Replies are listed 'Best First'.
Re^6: DBI messes up sleep
by ikegami (Patriarch) on Sep 17, 2007 at 19:37 UTC
    I didn't (even try to) reproduce it, and what I posted isn't a workaround. sleep should always be called in a loop to either handle or ignore signals.

      Hmm, just read http://perldoc.perl.org/functions/sleep.html and while it doesn't say excatly that, it does say that sleep doesn't neccessarily sleep the full length. It is certainly counter intuitive to me at least, if sleep for 30 i expect it to sleep for 30 seconds, guess i better change my expectations.


      ___________
      Eric Hodges
        "May be interrupted if the process receives a signal". Perhaps you could avoid the loop if you knew more (possibly system-specific) details. I'm working from that line and reports here on Perl Monks of signals interrupting sleep.