LinuxGuruz
  • Last 5 Forum Topics
    Replies
    Views
    Last post


The Web Only This Site
  • BOOKMARK

  • ADD TO FAVORITES

  • REFERENCES


  • MARC

    Mailing list ARChives
    - Search by -
     Subjects
     Authors
     Bodies





    FOLDOC

    Computing Dictionary




  • Text Link Ads






  • LINUX man pages
  • Linux Man Page Viewer


    The following form allows you to view linux man pages.

    Command:

    ualarm

    
    
    

    SYNOPSIS

           #include <unistd.h>
    
           useconds_t ualarm(useconds_t usecs, useconds_t interval);
    
       Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
    
           ualarm():
               Since glibc 2.12:
                   _BSD_SOURCE ||
                       (_XOPEN_SOURCE >= 500 ||
                           _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED) &&
                       !(_POSIX_C_SOURCE >= 200809L || _XOPEN_SOURCE >= 700)
               Before glibc 2.12:
                   _BSD_SOURCE || _XOPEN_SOURCE >= 500 ||
                   _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED
    
    
    

    DESCRIPTION

           The ualarm() function causes the signal  SIGALRM  to  be  sent  to  the
           invoking  process  after (not less than) usecs microseconds.  The delay
           may be lengthened slightly by any system activity or by the time  spent
           processing the call or by the granularity of system timers.
    
           Unless  caught  or  ignored, the SIGALRM signal will terminate the pro-
           cess.
    
           If the interval argument is nonzero, further SIGALRM  signals  will  be
           sent every interval microseconds after the first.
    
    
    

    RETURN VALUE

           This  function  returns  the  number  of microseconds remaining for any
           alarm that was previously set, or 0 if no alarm was pending.
    
    
    

    ERRORS

           EINTR  Interrupted by a signal.
    
           EINVAL usecs or interval is not  smaller  than  1000000.   (On  systems
                  where that is considered an error.)
    
    
    

    ATTRIBUTES

       Multithreading (see pthreads(7))
           The ualarm() function is thread-safe.
    
    
    

    CONFORMING TO

           4.3BSD,   POSIX.1-2001.    POSIX.1-2001  marks  ualarm()  as  obsolete.
           POSIX.1-2008 removes the specification of ualarm().  4.3BSD, SUSv2, and
           POSIX do not define any errors.
    
    
    

    NOTES

           POSIX.1-2001  does not specify what happens if the usecs argument is 0.
           On Linux (and probably most other systems), the effect is to cancel any
           pending alarm.
    
    
    

    SEE ALSO

           alarm(2),    getitimer(2),   nanosleep(2),   select(2),   setitimer(2),
           usleep(3), time(7)
    
                                      2013-12-23                         UALARM(3)
    
  • MORE RESOURCE


  • Linux

    The Distributions





    Linux

    The Software





    Linux

    The News



  • MARKETING






  • Toll Free

webmaster@linuxguruz.com
Copyright © 1999 - 2016 by LinuxGuruz