01-31-2003
4 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am looking for some coding standards for Unix Shell Scripting. Can anyone help me out in this?
Regards,
Himanshu (3 Replies)
Discussion started by: himanshu_s
3 Replies
2. Programming
I'm new to UNIX programming. I'm used to starting my program's versions at 1.0, but I look at all the UNIX programs out there and see things like 0.000.1 or 3.3.000 and I'm wondering what these things really mean. Do people just type anything they feel in there? Are things in pre-release... (6 Replies)
Discussion started by: hirni
6 Replies
3. Solaris
Hi All,
Thanks in advance for reading and any posts.
I was wondering if anyone has come across or can recomend or has any security standards that we could implement. We are running production Oracle systems on Solaris 8 boxes (which are global). We are after security considerations... (4 Replies)
Discussion started by: B14speedfreak
4 Replies
4. Programming
Hello Friends,
I am a newbie and have started using different compilers and tools to make myself familiar with their workings. I wanted to know that how compliant is gcc with the C++ standards. It is pretty obvious that no compiler is close to being completely compliant, but if there are some... (7 Replies)
Discussion started by: hthapar
7 Replies
LEARN ABOUT CENTOS
trace-cmd-check-events
TRACE-CMD-CHECK_EV(1) TRACE-CMD-CHECK_EV(1)
NAME
trace-cmd-check-events - parse the event formats on local system
SYNOPSIS
trace-cmd check-events [OPTIONS]
DESCRIPTION
The trace-cmd(1) check-events parses format strings for all the events on the local system. It returns whether all the format strings can
be parsed correctly. It will load plugins unless specified otherwise.
This is useful to check for any trace event format strings which may contain some internal kernel function references which cannot be
decoded outside of the kernel. This may mean that either the unparsed format strings of the trace events need to be changed or that a
plugin needs to be created to parse them.
OPTIONS
-N - Don't load plugins
SEE ALSO
trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1), trace-cmd-split(1),
trace-cmd-list(1), trace-cmd-listen(1), trace-cmd-start(1)
AUTHOR
Written by Vaibhav Nagarnaik, <vnagarnaik@google.com[1]>
RESOURCES
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
COPYING
Copyright (C) 2011 Google, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).
NOTES
1. vnagarnaik@google.com
mailto:vnagarnaik@google.com
06/11/2014 TRACE-CMD-CHECK_EV(1)