What are you trying to accomplish - displaying time is not anything like a usual requirement. Besides you will need a really fine grained timer to do this. Many commands in ksh shell are builtins and run with very little elapsed time.
In other words what is the purpose of timing each command? Performance analysis? See if
- as the first line of code, doesn't help you.
Hi all
I want to know the commands executed a by particular user .. for the whole day on my machine.
I have checked out with the commad
$lastcomm <user>
It is throwing an error called: ..
/var/adm/pacct: No such file or directory
Can u help me in this regard..
Thank U... (3 Replies)
Hi all,
I am new to unix OS.
Commands(external commands) given by the user are examined by shell and later executed by kernel.
Now I want to know how the internal(built in) commands are executed.
Please clarify whether they are executed directly by shell or by kernel.
Thanks in... (2 Replies)
Hi,
I have executed a set of commands on the linux server and later rebooted the server. Is it possible to get the details of the commands I executed prior to the reboot? If yes please let me know how?
Thanks. (1 Reply)
Dear friends,
Whenever I do logout from a session initiated by ssh/su, I need to print a small report which says the login time, logout time, commands got executed..
How can it be done?
I know when doing ssh, .profile file will get executed. Shall we do something with the help of it. (1 Reply)
hi,
Do anybody know, how to list out all the commands & scripts used by the user & root along with the timestamps under ksh & csh shells.
Thanks in advance
Regards
BS (1 Reply)
Here is two time I have:
Jul 12 16:02:01
Jul 13 01:02:01
and how can I do a simple match to get difference between two time which is 09:00:00
Thanks in advance. (3 Replies)
Hi,
I have cleared the commands by using >$HOME/.sh_history.
But if i issue HISTORY it shows some reference numbers but not the commands executed.
But i want to truncate those line numbers too.
May i know how i can achieve this?
Thanks (1 Reply)
On Solaris 10 server the system date won't match with the timestamp on files created by a cron jobs, Please help
here is what i get when i check for system date
infodba-ie10ux014:/tcpdv1_ie10/tcadmin/bin\n\r-> date
Tue Apr 24 15:27:43 GMT 2012at same time i executed a cron job, and checked... (4 Replies)
Discussion started by: karghum
4 Replies
LEARN ABOUT DEBIAN
io::async::timer::periodic
IO::Async::Timer::Periodic(3pm) User Contributed Perl Documentation IO::Async::Timer::Periodic(3pm)NAME
"IO::Async::Timer::Periodic" - event callback at regular intervals
SYNOPSIS
use IO::Async::Timer::Periodic;
use IO::Async::Loop;
my $loop = IO::Async::Loop->new;
my $timer = IO::Async::Timer::Periodic->new(
interval => 60,
on_tick => sub {
print "You've had a minute
";
},
);
$timer->start;
$loop->add( $timer );
$loop->run;
DESCRIPTION
This subclass of IO::Async::Timer implements repeating events at regular clock intervals. The timing may or may not be subject to how long
it takes the callback to execute. Iterations may be rescheduled runs at fixed regular intervals beginning at the time the timer was
started, or by a fixed delay after the previous code has finished executing.
For a "Timer" object that only runs a callback once, after a given delay, see instead IO::Async::Timer::Countdown. A Countdown timer can
also be used to create repeating events that fire at a fixed delay after the previous event has finished processing. See als the examples
in "IO::Async::Timer::Countdown".
EVENTS
The following events are invoked, either using subclass methods or CODE references in parameters:
on_tick
Invoked on each interval of the timer.
PARAMETERS
The following named parameters may be passed to "new" or "configure":
on_tick => CODE
CODE reference for the "on_tick" event.
interval => NUM
The interval in seconds between invocations of the callback or method. Cannot be changed if the timer is running.
first_interval => NUM
Optional. If defined, the interval in seconds after calling the "start" method before the first invocation of the callback or
method. Thereafter, the regular "interval" will be used. If not supplied, the first interval will be the same as the others.
Even if this value is zero, the first invocation will be made asynchronously, by the containing "Loop" object, and not
synchronously by the "start" method itself.
reschedule => STRING
Optional. Must be one of "hard", "skip" or "drift". Defines the algorithm used to reschedule the next invocation.
"hard" schedules each iteration at the fixed interval from the previous iteration's schedule time, ensuring a regular repeating
event.
"skip" schedules similarly to "hard", but skips over times that have already passed. This matters if the duration is particularly
short and there's a possibility that times may be missed, or if the entire process is stopped and resumed by "SIGSTOP" or similar.
"drift" schedules each iteration at the fixed interval from the time that the previous iteration's event handler returns. This
allows it to slowly drift over time and become desynchronised with other events of the same interval or multiples/fractions of it.
Once constructed, the timer object will need to be added to the "Loop" before it will work. It will also need to be started by the "start"
method.
AUTHOR
Paul Evans <leonerd@leonerd.org.uk>
perl v5.14.2 2012-10-24 IO::Async::Timer::Periodic(3pm)