Try using the full power of find. -type f restricts the search to regular files, so it excludes directories. The "*" is not needed because find looks at all files by default. if you wanted filenames that end in dat, then -name '*dat' would be required.
Hi guys,
I have set up multiple virtual FTP servers on a server through one physical NIC. I believe there are to ways; setting logical or alias ip's. I would like to know what is the difference between setting up a logical ip or setting up an alias ip to a physical network interface? Some links to... (5 Replies)
I am trying to create an alias for a frequently used directory path by using
alias xyz="/proj/dir_name"
and then trying to reach a sub-directoy by using
cd xyz/abc
but I get an error saying " No such file or directory "
plz tell me wats wrong with this ... (3 Replies)
Hello,
I need the command to create alias for a file "FILE" (NOT for commands) ? And Is there any difference between creating alias for files and creating alias for commands ?
For info, i'm using Solaris 8
Thx,
http://www.unix.com/images/misc/progress.gif (5 Replies)
Hello,
I want to create an alias for this command:
grep -i "<keyword_to_search>" <path_to_search>
Here's the alias I intended to make:
alias k 'set ARGS1 =(\!1); set ARGS2 =(\!2); grep -i "$ARGS1" ARGS2'
So that next time, for example, if I want to search the keyword "Help" in the path... (5 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Here is what I am supposed to do, word for word from my assignment page:
1. Create/modify and print a... (2 Replies)
I would like to create an alias on my 'grep' command on Linux.
Generally when I use 'grep', I do as follows:
$ ps -ef | grep -i ntp | grep -v grep
My question is how can I simply run the 'grep' command as shown above and it also include the -i / -v switches as well w/o me having to enter... (1 Reply)
I am trying to make a script that has grep finding lines that I get from the cat command, that start with something and end with an argument. I can get the first part, but whenever I try to add on the part that looks at the end of the line too, it stops working. Any ideas why? Here is my script:
... (11 Replies)
Hi all,
I am using SPARC Solaris 11.1 with EFI labelled disks.
I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs.
EFI labels use sectors and blocks and I am not sure how exactly it works.
From here I can try and create a... (2 Replies)
Hi everyone,
I have a custom kickstart file from a software vendor and I'm trying to package that with a RHEL 6.5 and then attach it to a VM and install RHEL with the settings in the kickstarter file. I'm doing this from a windows PC using an app called InfraRecorder.
I've extracted the... (0 Replies)
Discussion started by: 911Eric
0 Replies
LEARN ABOUT CENTOS
trace-cmd-split
TRACE-CMD-SPLIT(1)TRACE-CMD-SPLIT(1)NAME
trace-cmd-split - split a trace.dat file into smaller files
SYNOPSIS
trace-cmd split [OPTIONS] [start-time [end-time]]
DESCRIPTION
The trace-cmd(1) split is used to break up a trace.dat into small files. The start-time specifies where the new file will start at. Using
trace-cmd-report(1) and copying the time stamp given at a particular event, can be used as input for either start-time or end-time. The
split will stop creating files when it reaches an event after end-time. If only the end-time is needed, use 0.0 as the start-time.
If start-time is left out, then the split will start at the beginning of the file. If end-time is left out, then split will continue to the
end unless it meets one of the requirements specified by the options.
OPTIONS -i file
If this option is not specified, then the split command will look for the file named trace.dat. This options will allow the reading of
another file other than trace.dat.
-o file
By default, the split command will use the input file name as a basis of where to write the split files. The output file will be the
input file with an attached '.#' to the end: trace.dat.1, trace.dat.2, etc.
This option will change the name of the base file used.
-o file will create file.1, file.2, etc.
-s seconds
This specifies how many seconds should be recorded before the new file should stop.
-m milliseconds
This specifies how many milliseconds should be recorded before the new file should stop.
-u microseconds
This specifies how many microseconds should be recorded before the new file should stop.
-e events
This specifies how many events should be recorded before the new file should stop.
-p pages
This specifies the number of pages that should be recorded before the new file should stop.
Note: only one of *-p*, *-e*, *-u*, *-m*, *-s* may be specified at a time.
If *-p* is specified, then *-c* is automatically set.
-r
This option causes the break up to repeat until end-time is reached (or end of the input if end-time is not specified).
trace-cmd split -r -e 10000
This will break up trace.dat into several smaller files, each with at most
10,000 events in it.
-c
This option causes the above break up to be per CPU.
trace-cmd split -c -p 10
This will create a file that has 10 pages per each CPU from the input.
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-list(1), trace-cmd-listen(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-SPLIT(1)