POSIX compliance... Post: 302976999

Sponsored Content

Operating Systems OS X (Apple) POSIX compliance... Post 302976999 by drl on Sunday 10th of July 2016 09:43:01 PM

07-10-2016

Registered User

Hi.

Also:

Code:

            For delays of finer granularity than one second, the Time::HiRes
            module (from CPAN, and starting from Perl 5.8 part of the standard
            distribution) provides usleep(). You may also use Perl's
            four-argument version of select() leaving the first three
            arguments undefined, or you might be able to use the "syscall"
            interface to access setitimer(2) if your system supports it. See
            perlfaq8 for details.

Excerpt from perldoc -f sleep

For example:

Code:

#!/usr/bin/env perl

# @(#) p1       Demonstrate usleep;

use Time::HiRes qw( usleep nanosleep );

$microseconds = 2500000;
usleep($microseconds);

# nanosleep ($nanoseconds);

exit(0);

which would produce something like:

Code:

time ./p1

real    0m2.514s
user    0m0.008s
sys     0m0.000s

On an older OS/X:

Code:

OS, ker|rel, machine: Apple/BSD, Darwin 9.8.0, Power Macintosh
Distribution        : Mac OS X 10.5.8 (leopard, workstation)
perl 5.8.8

real    0m2.578s
user    0m0.045s
sys     0m0.021s

Best wishes ... cheers, drl

Last edited by drl; 07-10-2016 at 11:02 PM..

This User Gave Thanks to drl For This Post:

drl

View Public Profile for drl

Find all posts by drl

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Hello, I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password. This scares me, for a bunch of reasons. Mainly, one is that we...

2. UNIX for Dummies Questions & Answers

man synopsis standard compliance

In different online sources, I found bits and pieces of information about those square and angular brackets and pipes. From what I have read, I can conclude it looks like this: 1. Options outside any brackets are mandatory 2. Options inside these < .. > are mandatory too 3. Options inside ...

3. Cybersecurity

PCI DSS Compliance : Insecure Communication Has Been Detected

From the nessus scanner tool report i got below vulnerability PCI DSS Compliance : Insecure Communication Has Been Detected http://www.tenable.com/plugins/index.php?view=single&id=56208 As per the description given in above link - I am not able to understand How to find insecure port...

4. Red Hat

Looking for PCI Compliance tool for Redhat Lix.

Hi i am in new to Linux world . I have been assigned to a project to find out a tool that will fulfill the PCI compliance for Linux servers for Audit process. anyone have any recommendation on that. Do Rad hat have any native application or plug-ins which we can use for that.

5. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:...

LEARN ABOUT SUSE

usleep

USLEEP(3)						     Linux Programmer's Manual							 USLEEP(3)

NAME

       usleep - suspend execution for microsecond intervals

SYNOPSIS

       #include <unistd.h>

       int usleep(useconds_t usec);

   Feature Test Macro Requirements for glibc (see feature_test_macros(7)):

       usleep(): _BSD_SOURCE || _XOPEN_SOURCE >= 500

DESCRIPTION

       The  usleep() function suspends execution of the calling process for (at least) usec microseconds.  The sleep may be lengthened slightly by
       any system activity or by the time spent processing the call or by the granularity of system timers.

RETURN VALUE

       0 on success, -1 on error.

ERRORS

       EINTR  Interrupted by a signal; see signal(7).

       EINVAL usec is not smaller than 1000000.  (On systems where that is considered an error.)

CONFORMING TO

       4.3BSD, POSIX.1-2001.  POSIX.1-2001 declares this function obsolete; use nanosleep(2) instead.  POSIX.1-2008 removes the  specification	of
       usleep().

       On the original BSD implementation, and in glibc before version 2.2.2, the return type of this function is void.  The POSIX version returns
       int, and this is also the prototype used since glibc 2.2.2.

       Only the EINVAL error return is documented by SUSv2 and POSIX.1-2001.

NOTES

       The type useconds_t is an unsigned integer type capable of holding integers in the range [0,1000000].  Programs will be	more  portable	if
       they never mention this type explicitly.  Use

	   #include <unistd.h>
	   ...
	       unsigned int usecs;
	   ...
	       usleep(usecs);

       The  interaction  of  this  function  with  the	SIGALRM  signal,  and with other timer functions such as alarm(2), sleep(3), nanosleep(2),
       setitimer(2), timer_create(2), timer_delete(2), timer_getoverrun(2), timer_gettime(2), timer_settime(2), ualarm(3) is unspecified.

SEE ALSO

       alarm(2), getitimer(2), nanosleep(2), select(2), setitimer(2), sleep(3), ualarm(3), time(7)

COLOPHON

       This page is part of release 3.25 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

								    2007-07-26								 USLEEP(3)

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Discussion started by: rwallaceisg

2. UNIX for Dummies Questions & Answers

man synopsis standard compliance

Discussion started by: vkleban

3. Cybersecurity

PCI DSS Compliance : Insecure Communication Has Been Detected

Discussion started by: saurabh84g

4. Red Hat

Looking for PCI Compliance tool for Redhat Lix.

Discussion started by: sahasuman

5. HP-UX

Password compliance setting

Discussion started by: anaigini45

LEARN ABOUT SUSE

usleep