Hi! > According to POSIX, many historical implementations (including Version 7 > and System V) allow an alarm to occur up to a second early. Other > implementations allow alarms up to half a second or one clock tick early > or do not allow them to occur early at all. That means, the SIGALRM sent > by alarm() could arrive a little earlier. So, even if sem_wait() is > blocked, test could still fail. > Setting a range for time checking would be better. When sem_wait() is > block and then be interrupted by SIGALRM, if the time is in this range, > test is passed.
Out of curiosity, what system is this? The signal seems to arrives after more than 1 second on all linux boxes that I have. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
