i need a favour
if ( grep -i adding mpg* | grep -iv equation | ls -ctr | tail -1 ) # if it is not found
echo "log couldnot find "
else
var='grep -i adding mpg* | grep -iv equation | ls -ctr | tail -1'
for the above i am struggling with syntax
could someone please help me in that (1 Reply)
Hi,
I worte a script which runs perfect when i execute it manually. But when i scheduled into cron the grep command alone is not working.
the sample script,
/usr/bin/grep FTP $subfile > /tmp/tfsrec.dat
tfs=`echo $?`
if
then
echo "FTP FOUND"
else
echo "FTP NOT FOUND"
Where... (5 Replies)
Hi Folk,
Following is the command I used to get data related to the DataFlowEngine.
I wanted to know the % usage of cpu and memory.
ps avg | grep Data
This command will show the processes with its PID as :
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
... (1 Reply)
Hi,
I am very new to Unix script. Suppose i have a file with column header:
NAME1 NAME2 Address Tel
And I always need to make a file with column header:
ID NAME1 NAME2 EMail Address Tel
For the columns that do not exist in the file, I would still like to make a column with blank.
... (11 Replies)
I'd like to copy strings from a log file and put them into a CSV.
The strings could be on different line numbers, depending on size of log.
Example Log File:
File = foo.bat
Date = 11/11/11
User = Foo Bar
Size = 1024
...
CSV should look like:
"foo.bat","11/11/11","Foo Bar","1024" (7 Replies)
I have mail:
cat /home/oracle/scripts/dbsizedaily.txt | mail -s "$TODAY: PROD DB Size" $RECIPIENTS
I like to get and put USED_GB and %USED of the very last row from /home/oracle/scripts/dbsizedaily.txt.
/home/oracle/scripts/dbsizedaily.txt has :
DATE TIME TOTAL_GB USED_GB ... (6 Replies)
Discussion started by: Daniel Gate
6 Replies
LEARN ABOUT MOJAVE
procsystime
procsystime(1m) USER COMMANDS procsystime(1m)NAME
procsystime - analyse system call times. Uses DTrace.
SYNOPSIS
procsystime [-acehoT] [ -p PID | -n name | command ]
DESCRIPTION
procsystime prints details on system call times for processes, both the elapsed times and on-cpu times can be printed.
The elapsed times are interesting, to help identify syscalls that take some time to complete (during which the process may have slept). CPU
time helps us identify syscalls that are consuming CPU cycles to run.
Since this uses DTrace, only users with root privileges can run this command.
OPTIONS -a print all data
-c print syscall counts
-e print elapsed times, ns
-o print CPU times, ns
-T print totals
-p PID examine this PID
-n name
examine processes which have this name
EXAMPLES
Print elapsed times for PID 1871,
# procsystime -p 1871
Print elapsed times for processes called "tar",
# procsystime -n tar
Print CPU times for "tar" processes,
# procsystime -on tar
Print syscall counts for "tar" processes,
# procsystime -cn tar
Print elapsed and CPU times for "tar" processes,
# procsystime -eon tar
print all details for "bash" processes,
# procsystime -aTn bash
run and print details for "df -h",
# procsystime df -h
FIELDS
SYSCALL
System call name
TIME (ns)
Total time, nanoseconds
COUNT Number of occurrences
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
procsystime will sample until Ctrl-C is hit.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO dtruss(1M), dtrace(1M), truss(1)version 1.00 Sep 22, 2005 procsystime(1m)