If it is running, then there is a pid on stdout, and a new run will be a duplicate. By tying stdout to stderr, you can get the letters that say it is being run (not just viewed or whatever) (fuser puts pids and separating white space on stdout and all else on stderr).
You can write the job's pid in a control file named for the job, and search for a running copy that way, but fuser is cleaner and simpler. Binding a socket can be exclusive, too.
Hi there,
I would like to write a script which while running will kill and then execute again a task every 15 minutes.
Here's what I want to do:
Al Jazeera English have a low quality, time-limited 15 minute trial stream up at their site. I.e. when I click on the 56K link, it will play in... (0 Replies)
I am able to run the UNIX commands in a Windows box from a UNIX box through "SSH" functionality. But whenever the SSH connection is established between UNIX and Windows, password for windows box is being asked.
Is there a way to avoid asking password whenever the SSH connection is made? Can I... (1 Reply)
Hi,
I have the root id and the uid is always 0 for the root. Can i create another user say admin with the uid as 0? If so will it have the same privilege as that of user.
Will there be any effect while doing this?
lorcan (6 Replies)
I have a file contains
TASK gsnmpproxy {
CommandLine = $SMCHOME/bin/gsnmpProxy.exe
}
TASK gsnmpdbgui {
CommandLine = $SMCHOME/bin/gsnmpdbgui.exe
I would like to comment and than uncomment specific task eg TASK gsnmpproxy
Pls suggest how to do in shell script (9 Replies)
I have an task definition listing xml file that contains a list of tasks such as
<TASKLIST
<TASK definition="Completion date" id="Taskname1" Some other
<CODE name="Code12"
<Parameter pname="Dog" input="5.6" units="feet" etc /Parameter>
<Parameter... (3 Replies)
Sometimes we need a single instance of a script to run at a time. Meaning, the script itself should detects whether any instances of himself are still running and act accordingly.
When multiple instances of one script running, it’s easy to cause problems. I’ve ever seen that about 350 instances... (4 Replies)
Hi folks!
I need you help to discover what's the impact of a duplicated UID in an operating system. What's the meaning when someone put in different users the same UID? (3 Replies)
Hello all..
i have few task to do on specific day ar per weekday or weekend...
for example i have 3 tasks:
task1
task2
task3
Now i need to create a shell script
If it is weekday it will change the status of these tasks as below
sendevent -E CHANGE_STATUS -s SUCCESS -J task1... (4 Replies)
i have the following code:
APIDS=$(echo $(ps -ef | awk -v gpid="${gpid}" '$2 == gpid || $3 == gpid {print $2,$3}') | sed 's~ ~|~g')
AllProcs=$(ps -ef | awk -v allpids="${APIDS}" '$2 ~ allpids || $3 ~ allpids {print $0}' | sed '/^$/d')
it seems the above... (6 Replies)
Discussion started by: SkySmart
6 Replies
LEARN ABOUT DEBIAN
iv_task
iv_task(3) ivykis programmer's manual iv_task(3)NAME
iv_task_register, iv_task_unregister, iv_task_registered - deal with ivykis tasks
SYNOPSIS
#include <iv.h>
struct iv_task {
void *cookie;
void (*handler)(void *);
};
void IV_TASK_INIT(struct iv_task *task);
void iv_task_register(struct iv_task *task);
void iv_task_unregister(struct iv_task *task);
int iv_task_registered(struct iv_task *task);
DESCRIPTION
The functions iv_task_register and iv_task_unregister register, respectively unregister, a task with the current thread's ivykis event
loop. iv_task_registered on a task returns true if that task is currently registered with ivykis.
A task is like a timer, but with an immediate timeout. When a task is registered, unless it is unregistered again first, the callback
function specified by ->handler is guaranteed to be called once, in the thread that the task was registered in, some time after control
returns to the ivykis main loop but before ivykis will sleep for more events, with ->cookie as its first and sole argument. When this hap-
pens, the task is transparently unregistered.
Tasks are mainly used for scheduling code for execution where it is not appropriate to directly run that code in the calling context (for
example, because the current context might be run as a callback function where the caller expects certain conditions to remain invariant
after the callback completes).
The application is allowed to change the ->cookie and ->handler members at any time.
A given struct iv_task can only be registered in one thread at a time, and a task can only be unregistered in the thread that it was regis-
tered from.
There is no limit on the number of tasks registered at once.
See iv_examples(3) for programming examples.
SEE ALSO ivykis(3), iv_examples(3)ivykis 2010-08-15 iv_task(3)