Sponsored Content
Top Forums Programming auto update on directory change Post 7677 by Neo on Saturday 29th of September 2001 10:13:58 AM
Old 09-29-2001
I suggest you look at opening the approproate directory and use the FD with select. Reading the select man page will help you formulate the strategy and algorithm.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

auto change filemanager folder colors dependent on location in directory hierarchy

Hello, Is it possible to make a file manager use different "colored folders" when browsing specific directories? For example, if I open a gnome file manager and browse my windows share at, smb://192.168.1.101/z/ , can I make those folders appear green? And when I open another instance of... (0 Replies)
Discussion started by: bz43
0 Replies

2. Web Development

How to auto update html page

is there any way to auto update html page. I created html page entry.html, whenever i change in html script i need to refresh my page. If not in html, can we do this in any other language and how? (2 Replies)
Discussion started by: RohitKJ
2 Replies

3. UNIX for Dummies Questions & Answers

auto change x screen and execute script

Hi there, I've been looking all day, but could not find anything helpfull, so I hope you can help me. When my system now starts up, the Xwindow is automaticly started and i get the log on screen (which is x screen 7 if I'm correct) Now what I would like is on startup that instead of going to... (1 Reply)
Discussion started by: Wonderke
1 Replies

4. Windows & DOS: Issues & Discussions

script to change widows update permissions

I want to allow windows update when ordinary users are logged on, I'm pretty sure that adjusting the permissions registry entry HEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/WindowsUpdate to allow acces to all domins users does the trick. I already have a logon.bat that runs at... (0 Replies)
Discussion started by: barrydocks
0 Replies

5. UNIX for Advanced & Expert Users

Update users password change time

Hello - Is this possible on Unix machines? Can we update user password change time? (6 Replies)
Discussion started by: manju--
6 Replies

6. UNIX for Dummies Questions & Answers

Auto Version update

We have a version for every file like RHZ 1.0 / Ver 1.4.2 etc. Whenever I place a new file with same file name i want the version to get auto upgraded. So can anyone suggest code.. Eg: RHX 1.0 -> RHZ 1.1 Ver 1.4.2. -> Ver 1.4.3 (1 Reply)
Discussion started by: krishna87
1 Replies

7. Shell Programming and Scripting

Change to directory and search some file in that directory in single command

I am trying to do the following task : export ENV=aaa export ENV_PATH=$(cd /apps | ls | grep $ENV) However, it's not working. What's the way to change to directory and search some file in that directory in single command Please help. (2 Replies)
Discussion started by: saurau
2 Replies

8. Shell Programming and Scripting

Shell Script for Auto IP Change

Hi, I am newbie to Linux/Asterisk. I am trying to write a shell script that would look for my SIP trunk registration, if found UNREACHABLE then it would execute a command and check my local IP, if my local IP is 192.168.1.106 then it would change the IP to 192.168.1.150 and vice versa, after... (8 Replies)
Discussion started by: jeetz
8 Replies
TIMER_GETOVERRUN(2)					     Linux Programmer's Manual					       TIMER_GETOVERRUN(2)

NAME
timer_getoverrun - get overrun count for a POSIX per-process timer SYNOPSIS
#include <time.h> int timer_getoverrun(timer_t timerid); Link with -lrt. Feature Test Macro Requirements for glibc (see feature_test_macros(7)): timer_getoverrun(): _POSIX_C_SOURCE >= 199309L DESCRIPTION
timer_getoverrun() returns the "overrun count" for the timer referred to by timerid. An application can use the overrun count to accu- rately calculate the number of timer expirations that would have occurred over a given time interval. Timer overruns can occur both when receiving expiration notifications via signals (SIGEV_SIGNAL), and via threads (SIGEV_THREAD). When expiration notifications are delivered via a signal, overruns can occur as follows. Regardless of whether or not a real-time signal is used for timer notifications, the system queues at most one signal per timer. (This is the behavior specified by POSIX.1-2001. The alternative, queuing one signal for each timer expiration, could easily result in overflowing the allowed limits for queued signals on the system.) Because of system scheduling delays, or because the signal may be temporarily blocked, there can be a delay between the time when the notification signal is generated and the time when it is delivered (e.g., caught by a signal handler) or accepted (e.g., using sigwait- info(2)). In this interval, further timer expirations may occur. The timer overrun count is the number of additional timer expirations that occurred between the time when the signal was generated and when it was delivered or accepted. Timer overruns can also occur when expiration notifications are delivered via invocation of a thread, since there may be an arbitrary delay between an expiration of the timer and the invocation of the notification thread, and in that delay interval, additional timer expirations may occur RETURN VALUE
On success, timer_getoverrun() returns the overrun count of the specified timer; this count may be 0 if no overruns have occurred. On failure, -1 is returned, and errno is set to indicate the error. ERRORS
EINVAL timerid is not a valid timer ID. VERSIONS
This system call is available since Linux 2.6. CONFORMING TO
POSIX.1-2001 NOTES
When timer notifications are delivered via signals (SIGEV_SIGNAL), on Linux it is also possible to obtain the overrun count via the si_overrun field of the siginfo_t structure (see sigaction(2)). This allows an application to avoid the overhead of making a system call to obtain the overrun count, but is a nonportable extension to POSIX.1-2001. POSIX.1-2001 only discusses timer overruns in the context of timer notifications using signals. BUGS
POSIX.1-2001 specifies that if the timer overrun count is equal to or greater than an implementation-defined maximum, DELAYTIMER_MAX, then timer_getoverrun() should return DELAYTIMER_MAX. However, Linux does not implement this feature: instead, if the timer overrun value exceeds the maximum representable integer, the counter cycles, starting once more from low values. EXAMPLE
See timer_create(2). SEE ALSO
clock_gettime(2), sigaction(2), signalfd(2), sigwaitinfo(2), timer_create(2), timer_delete(2), timer_settime(2), signal(7), 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/. Linux 2009-02-20 TIMER_GETOVERRUN(2)
All times are GMT -4. The time now is 06:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy