hello everyone. im sure someone has run into the problem of timestamping files and end up haveing 2 files with the same name thus over writeing one of them.
In my application i am trying to get a timestamp w/ milliseconds but i am haveing no luck and finding an answer in the man pages.
I know... (3 Replies)
I use something like this in perl to get the date and time:
use Time::localtime;
use Time::gmtime;
$tm = gmtime;
$time_str = sprintf "%04d-%02d-%02d %02d:%02d:%02d",
$tm->year + 1900, $tm->mon + 1, $tm->mday,
$tm->hour, $tm->min, $tm->sec;
It gives me something like this:
2010-08-26... (1 Reply)
Hey everyone,
I'm coming from Linux where the top command gave me lots of process
info (particularly CPU time in milliseconds) and I'm trying to find
similar info in Solaris.
So far I've looked at prstat and ps but neither give cpu time in
milliseconds, both seem to have 1 second... (2 Replies)
I need to put a small delay into a shell script. I'm looking for something smaller than "sleep" - a second is way too long. I want to sleep something like 10 milliseconds. I've tried "usleep" and "nanosleep", but the script doesn't recognize them.
I'm using the bash shell but I'm willing to... (9 Replies)
Hi,
I need to find the difference between 2 dates in SunOS 5.10
input will be in(yyyymmdd)
date1: 20131011
date2:20131012
my output shold be diff between two dates i.e 0,1,2,3 date2 is always greater than date1.
if it handles even leap year then it wil be more helpful.
thank u... (2 Replies)
while I load the value using sqlldr the millisecond values not stored in oracle table.
Value:
'26-OCT-17 08.59.50.916000000 AM'
CTL field:
SRC_SYS_CRT_TS Position(23:48) "decode(:SRC_SYS_CRT_TS,null,sysdate-1,to_timestamp(:SRC_SYS_CRT_TS,'yyyy-mm-dd.hh24.mi.ss.FF'))",
... (1 Reply)
Discussion started by: priya1987
1 Replies
LEARN ABOUT CENTOS
trace-cmd-listen
TRACE-CMD-LISTEN(1)TRACE-CMD-LISTEN(1)NAME
trace-cmd-listen - listen for incoming connection to record tracing.
SYNOPSIS
trace-cmd listen -p port [OPTIONS]
DESCRIPTION
The trace-cmd(1) listen sets up a port to listen to waiting for connections from other hosts that run trace-cmd-record(1) with the -N
option. When a connection is made, and the remote host sends data, it will create a file called trace.HOST:PORT.dat. Where HOST is the name
of the remote host, and PORT is the port that the remote host used to connect with.
OPTIONS -p port
This option will specify the port to listen to.
-D
This options causes trace-cmd listen to go into a daemon mode and run in the background.
-d dir
This option specifies a directory to write the data files into.
-o filename
This option overrides the default trace in the trace.HOST:PORT.dat that is created when a remote host connects.
-l filename
This option writes the output messages to a log file instead of standard output.
SEE ALSO trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1),
trace-cmd-split(1), trace-cmd-list(1)AUTHOR
Written by Steven Rostedt, <rostedt@goodmis.org[1]>
RESOURCES
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
COPYING
Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).
NOTES
1. rostedt@goodmis.org
mailto:rostedt@goodmis.org
06/11/2014 TRACE-CMD-LISTEN(1)