So you want to verify:
3 files arrive at 03:00 UST for AWS (A,B,C)
3 files arrive at 10:00 UST for EMEA (X,Y,Z)
5 files arrive at 23:00 UST for APJ (e,f,g,h,i)
Questions:
Do any of the files ever arrive late or early?
A lot more information would be useful. And I do not know tidal syntax. You will have to come up with that
Or your UNIX OS or any actual file names.
Do the files get deleted before the next time they arrive?
The OS is REALLY important. If I were to give you a solution that works on all "platforms everywhere answer" it will not be optimal
Logic:
Now answer some questions so we can help you.
Hi,
Whats the command for finding files older then 20mins. This has to be part of the find command as it will be part of a cleanup script.
thanks
Budrito (4 Replies)
Hi,
I have some log files created in the following fashion
Ex:
file name modified date
1) s.log1 01-jan-08
2) s.log2 02-jan-08
3) s.log3 03-jan-08
4) s.log4 04-jan-08
Now I want to have the latest 2 logs and delete the others.
Can you tell me the one liner /... (1 Reply)
Hi All,
I know the timestamp of a file. Now i would like to list all the files in the with the same time stamp in the same file.
Any help would be appreciated.
Thanks.
sunny (1 Reply)
Hi,
I have a requirement ,let us say 1000 files needs to be transferred in an hour from one path to another path and if the files (1000 files) are transferred within an hour ( say 40 mins), then the process should remain idle for the remaining time ( 20 mins). (3 Replies)
Dear All,
Pls help me on this issue.
i want to write a script to check whether files updation happening in cuttent time or not.
i have set of files in directory which wil update in time basis..
Requirement: If the files are updating in system time i just want to print "files are... (6 Replies)
Hi ,
please guide me for a bash script that will create a txt files and the name of the txt files will be as of timestamp so that each file name will be different from other and these files will be get created say after every 10 minutes in a folder(/home/p2000/sxs137), please guide me how would... (1 Reply)
Hi friends,
I am trying to check if the two files i am expecting are created in a specific location.
if both files does not exist, do an echo
if -a ]; then
echo "files not found"
fi
It gives me the following message:
bash: Please help! :) (3 Replies)
Hey guys,
Sorry for the basic question but I have a lot of files that I want to separate into groups based on filenames which I can then cat together. Eg I have:
(a_b_c.txt)
WB34_2_SLA8.txt
WB34_1_SLA8.txt
WB34_1_DB10.txt
WB34_2_DB10.txt
WB34_1_SLA8.txt
WB34_2_SLA8.txt
77_1_SLA8.txt... (1 Reply)
Hi All,
I have scenario where I need to zip huge number of DB audit log files newer than 90 days and delete anything older than that. If the files are too huge in number,zipping will take long time and causing CPU spikes. To avoid this I wanted to segregate files based on how old they are and... (2 Replies)
I created this script for check whether specific files exist or not in the given location. but when I run this its always showing
Failed - Flag_lms_device_info_20160628.txt do not exist
Failed - Flag_lms_weekly_usage_info_20160628.txt do not exist
but both files are existing. appreciate help... (2 Replies)
Discussion started by: lfreez
2 Replies
LEARN ABOUT DEBIAN
lttng-gen-tp
LTTNG-GEN-TP(1)LTTNG-GEN-TP(1)NAME
lttng-gen-tp -- LTTng UST 2.0 tracepoint code generator
SYNOPSIS
lttng-gen-tp [OPTIONS] TEMPLATE_FILE
DESCRIPTION
The LTTng project aims at providing highly efficient tracing tools for Linux. It's tracers help tracking down performance issues and
debugging problems involving multiple concurrent processes and threads. Tracing across multiple systems is also possible.
The lttng-gen-tp tool simplify the generation of the UST tracepoint files. It takes a simple template file and generate the necessary code
to use the defined tracepoints in your application. The section TEMPLATE FILE FORMAT describe the content of the template file.
Currently, the tool can generate the .h, .c and .o associated to your tracepoint. The generated .h can be directly included in your appli-
cation. You can let the tool generate the .o or compile the .c yourself. You can compile the .c into a .o, .a or .so at your choice and
link it with your application. Refer to the UST documentation for the advantages and disadvantage of each form. To compile the resulting
.c file, you need to add the options "-llttng-ust -I.". Note for C++ support: although an application instrumented with tracepoints can be
compiled with g++, tracepoint probes should be compiled with gcc (only tested with gcc so far).
OPTIONS
This program follow the usual GNU command line syntax with long options starting with two dashes. Below is a summary of the available
options.
-h, --help
Show summary of possible options and commands.
-v, --verbose
Increase verbosity.
-o, --output
Specify the generated file. The type of the generated file depend on the file extension (.h, .c, .o). This option can be specfied
multiple times to generate different file type.
When no output is specified de default files are generated with the same base filename as the template file. The default files are: .h, .c,
.o.
TEMPLATE FILE FORMAT
The template file, which has the usual extension .tp, contains a list of TRACEPOINT_EVENT definitions and other optional definition entries
like TRACEPOINT_LOGLEVEL. (See lttng-ust(3) for the complete list of available definition.)
You write them as you would write them in a C header file. You can add comments with /* */, // and #.
The provider name (the first field of TRACEPOINT_EVENT) must be the same for the whole file.
Example
TRACEPOINT_EVENT(
sample_tracepoint,
message, // Comment
TP_ARGS(char *, text),
/* Next are the fields */
TP_FIELDS(
ctf_string(message, text)
)
)
ENVIRONMENT VARIABLES
When the tool generate an .o file, it will look for the following environment variables
CC Specifer which C compiler to use. If the variable is not specified, the tool will try "cc" and "gcc"
CFLAGS Flags directly passed to the compiler
SEE ALSO lttng-ust(3), lttng(1)BUGS
If you encounter any issues or usability problem, please report it on our mailing list <lttng-dev@lists.lttng.org> to help improve this
project.
CREDITS
lttng-gen-tp is distributed under the GNU General Public License version 2. See the file COPYING for details.
A Web site is available at http://lttng.org for more information on the LTTng project.
You can also find our git tree at http://git.lttng.org.
Mailing lists for support and development: <lttng-dev@lists.lttng.org>.
You can find us on IRC server irc.oftc.net (OFTC) in #lttng.
AUTHORS
lttng-gen-tp is written by Yannick Brosseau <yannick.brosseau@gmail.com>.
February 16, 2012 LTTNG-GEN-TP(1)