10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I would like to know what this command means?
PID=$!
what does "!" stand for? (5 Replies)
Discussion started by: googlietdr
5 Replies
2. UNIX for Dummies Questions & Answers
name the process wit PID value 0? swapper or scheduler or both.... (3 Replies)
Discussion started by: karthi_g
3 Replies
3. UNIX for Dummies Questions & Answers
I have searched to find an anwer to no avail, I hope you can help me.
I have a.ksh that many people call and a.ksh calls b.ksh
b.ksh is also invoked stand-alone by many people as well
In b.ksh I want to do something different if it was not involked by a.ksh.
How can I do this? (7 Replies)
Discussion started by: CAGIRL
7 Replies
4. UNIX for Dummies Questions & Answers
Hello people,
This question might seem to be a little naive but here it goes:
I want to know the PID of a script that is running in the background.
eg: There is a script called Data_Downloader.sh
I am using the command:
ps -ef | grep Data_Downloader.sh
But I am getting the output as
wrkarea... (9 Replies)
Discussion started by: Rajat
9 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I need to get the pid of a process and have to store the pid in a variable and i want to use this value(pid) of the variable for some process. Please can anyone tell me how to get the pid of a process and store it in a variable. please help me on this.
Thanks in advance,
Amudha (7 Replies)
Discussion started by: samudha
7 Replies
6. Shell Programming and Scripting
Hi All,
In my project i have two process runs in the back end.
Once i start my project, and execute the command ps, i get below output:
PID TTY TIME CMD
9086 pts/1 0:00 ksh
9241 pts/1 0:02 java
9240 pts/1 0:00 shell_script_bg
java with 9241 PID is the main... (4 Replies)
Discussion started by: rkrgarlapati
4 Replies
7. UNIX for Dummies Questions & Answers
1. If I use an software application(which connects to the database in the server) in my local pc, how many PID should be registered? Would there be PID for the session and another PID for socket connection?
2. I noticed (through netstat) that when I logged in using the my software application,... (1 Reply)
Discussion started by: pcx26
1 Replies
8. UNIX for Dummies Questions & Answers
Hi ,
I am trying to get the PID using the following command:
$ /usr/ucb/ps -auwwwwx | grep java | grep Proceess | ptree PID or
$ /usr/ucb/ps -auwwwwx | grep java | grep Proceess;ptree PID
it is possible to get PID, such that I check whether any orphan
process is running.
solution... (0 Replies)
Discussion started by: Rakesh Bhat
0 Replies
9. Shell Programming and Scripting
The below command returns full line.How can i get only PID from this line ie 15794 from the below example
(FI NY) nbswpsa52.ny.ficc.gs.com~ ->ps -ef | grep keepalive | grep -v keepaliveStub | grep -v swapback | grep -v grep
ficctprd 15794 1 0 13:12:58 ? 0:01 keepalive (3 Replies)
Discussion started by: kotasateesh
3 Replies
10. Programming
question: for the below program
i just printed the value for pid, child pid and parent pid
why does it give me 6 values? i assume ppid is 28086
but can't figure out why there are 5 values printed instead of just two!
can someone comment on that!
#include<stdio.h>
#define DIM 8
int... (3 Replies)
Discussion started by: a25khan
3 Replies
timer(3erl) Erlang Module Definition timer(3erl)
NAME
timer - Timer Functions
DESCRIPTION
This module provides useful functions related to time. Unless otherwise stated, time is always measured in milliseconds . All timer func-
tions return immediately, regardless of work carried out by another process.
Successful evaluations of the timer functions yield return values containing a timer reference, denoted TRef below. By using cancel/1 , the
returned reference can be used to cancel any requested action. A TRef is an Erlang term, the contents of which must not be altered.
The timeouts are not exact, but should be at least as long as requested.
EXPORTS
start() -> ok
Starts the timer server. Normally, the server does not need to be started explicitly. It is started dynamically if it is needed.
This is useful during development, but in a target system the server should be started explicitly. Use configuration parameters for
kernel for this.
apply_after(Time, Module, Function, Arguments) -> {ok, Tref} | {error, Reason}
Types Time = integer() in Milliseconds
Module = Function = atom()
Arguments = [term()]
Evaluates apply(M, F, A) after Time amount of time has elapsed. Returns {ok, TRef} , or {error, Reason} .
send_after(Time, Pid, Message) -> {ok, TRef} | {error,Reason}
send_after(Time, Message) -> {ok, TRef} | {error,Reason}
Types Time = integer() in Milliseconds
Pid = pid() | atom()
Message = term()
Result = {ok, TRef} | {error, Reason}
send_after/3 :
Evaluates Pid ! Message after Time amount of time has elapsed. ( Pid can also be an atom of a registered name.) Returns {ok,
TRef} , or {error, Reason} .
send_after/2 :
Same as send_after(Time, self(), Message) .
exit_after(Time, Pid, Reason1) -> {ok, TRef} | {error,Reason2}
exit_after(Time, Reason1) -> {ok, TRef} | {error,Reason2}
kill_after(Time, Pid)-> {ok, TRef} | {error,Reason2}
kill_after(Time) -> {ok, TRef} | {error,Reason2}
Types Time = integer() in milliseconds
Pid = pid() | atom()
Reason1 = Reason2 = term()
exit_after/3 :
Send an exit signal with reason Reason1 to Pid Pid . Returns {ok, TRef} , or {error, Reason2} .
exit_after/2 :
Same as exit_after(Time, self(), Reason1) .
kill_after/2 :
Same as exit_after(Time, Pid, kill) .
kill_after/1 :
Same as exit_after(Time, self(), kill) .
apply_interval(Time, Module, Function, Arguments) -> {ok, TRef} | {error, Reason}
Types Time = integer() in milliseconds
Module = Function = atom()
Arguments = [term()]
Evaluates apply(Module, Function, Arguments) repeatedly at intervals of Time . Returns {ok, TRef} , or {error, Reason} .
send_interval(Time, Pid, Message) -> {ok, TRef} | {error, Reason}
send_interval(Time, Message) -> {ok, TRef} | {error, Reason}
Types Time = integer() in milliseconds
Pid = pid() | atom()
Message = term()
Reason = term()
send_interval/3 :
Evaluates Pid ! Message repeatedly after Time amount of time has elapsed. ( Pid can also be an atom of a registered name.)
Returns {ok, TRef} or {error, Reason} .
send_interval/2 :
Same as send_interval(Time, self(), Message) .
cancel(TRef) -> {ok, cancel} | {error, Reason}
Cancels a previously requested timeout. TRef is a unique timer reference returned by the timer function in question. Returns {ok,
cancel} , or {error, Reason} when TRef is not a timer reference.
sleep(Time) -> ok
Types Time = integer() in milliseconds or the atom infinity
Suspends the process calling this function for Time amount of milliseconds and then returns ok , or suspend the process forever if
Time is the atom infinity . Naturally, this function does not return immediately.
tc(Module, Function, Arguments) -> {Time, Value}
tc(Fun, Arguments) -> {Time, Value}
Types Module = Function = atom()
Fun = fun()
Arguments = [term()]
Time = integer() in microseconds
Value = term()
tc/3 :
Evaluates apply(Module, Function, Arguments) and measures the elapsed real time as reported by now/0 . Returns {Time, Value} ,
where Time is the elapsed real time in microseconds , and Value is what is returned from the apply.
tc/2 :
Evaluates apply(Fun, Arguments) . Otherwise works like tc/3 .
now_diff(T2, T1) -> Tdiff
Types T1 = T2 = {MegaSecs, Secs, MicroSecs}
Tdiff = MegaSecs = Secs = MicroSecs = integer()
Calculates the time difference Tdiff = T2 - T1 in microseconds , where T1 and T2 probably are timestamp tuples returned from
erlang:now/0 .
seconds(Seconds) -> Milliseconds
Returns the number of milliseconds in Seconds .
minutes(Minutes) -> Milliseconds
Return the number of milliseconds in Minutes .
hours(Hours) -> Milliseconds
Returns the number of milliseconds in Hours .
hms(Hours, Minutes, Seconds) -> Milliseconds
Returns the number of milliseconds in Hours + Minutes + Seconds .
EXAMPLES
This example illustrates how to print out "Hello World!" in 5 seconds:
1> timer:apply_after(5000, io, format, ["~nHello World!~n", []]).
{ok,TRef}
Hello World!
The following coding example illustrates a process which performs a certain action and if this action is not completed within a certain
limit, then the process is killed.
Pid = spawn(mod, fun, [foo, bar]),
%% If pid is not finished in 10 seconds, kill him
{ok, R} = timer:kill_after(timer:seconds(10), Pid),
...
%% We change our mind...
timer:cancel(R),
...
WARNING
A timer can always be removed by calling cancel/1 .
An interval timer, i.e. a timer created by evaluating any of the functions apply_interval/4 , send_interval/3 , and send_interval/2 , is
linked to the process towards which the timer performs its task.
A one-shot timer, i.e. a timer created by evaluating any of the functions apply_after/4 , send_after/3 , send_after/2 , exit_after/3 ,
exit_after/2 , kill_after/2 , and kill_after/1 is not linked to any process. Hence, such a timer is removed only when it reaches its time-
out, or if it is explicitly removed by a call to cancel/1 .
Ericsson AB stdlib 1.17.3 timer(3erl)