Is that what the data looks like, or are the lines actually really long?
---------- Post updated at 11:06 AM ---------- Previous update was at 10:50 AM ----------
Will the process name always be NEWOLUF2?
---------- Post updated at 11:16 AM ---------- Previous update was at 11:06 AM ----------
Here's what I have so far, assuming the long lines were wrapped accidentally. It's much, much, much easier to write when you know what you're supposed to be operating on
Code:
$ cat begintrans.c
#include <stdio.h>
#include <string.h>
int main(void)
{
char buf[16384];
int transcount=0, elapsetotal=0;
while(!feof(stdin))
{
int newoluf=0, elapsetime=-1;
char timestamp[64]={0};
buf[0]='\0'; // Blank out buffer
while(strcmp(buf, "BEGINTRANS\n") != 0) // look for BEGINTRANS
if(fgets(buf, 16384, stdin) == NULL)
break; // EOF
if(feof(stdin)) break;
while(strcmp(buf, "ENDTRANS\n") != 0) // Look for ENDTRANS
{
const char *tsstr;
if(fgets(buf, 16384, stdin) == NULL)
break;
if(strstr(buf, "NEWOLUF2") != NULL)
newoluf=1;
if(tsstr=strstr(buf, "Timestamp"))
sscanf(tsstr, "Timestamp <%[^>]>", timestamp);
if(strncmp(buf, "ElapseTime", 10) == 0)
sscanf(buf, "ElapseTime <%d>", &elapsetime);
}
if((elapsetime>=0) && (timestamp[0]))
{
transcount++;
elapsetotal += elapsetime;
printf("trans %d, elapsetime %d, timestamp %s\n",
transcount, elapsetime, timestamp);
}
}
printf("Average elapsetime is %d\n", elapsetotal / transcount);
return(0);
}
$ gcc begintrans.c -o begintrans
$ ./begintrans < data
trans 1, elapsetime 745, timestamp 14Sep1111-07-37
trans 2, elapsetime 765, timestamp 14Sep1111-07-37
trans 3, elapsetime 579, timestamp 14Sep1111-07-37
trans 4, elapsetime 356, timestamp 14Sep1111-07-38
trans 5, elapsetime 651, timestamp 14Sep1111-07-41
trans 6, elapsetime 292, timestamp 14Sep1111-07-42
trans 7, elapsetime 345, timestamp 14Sep1111-07-52
Average elapsetime is 533
$
Why would you need to use this in a script?
Why can't you just use print to print out what you want printed in the begining and print for what you want at the end.
So this:
nawk 'BEGIN {print "this is the first line"}
{print $1 $2 $3}
{print $5 $6}
END {print "this is the last line"}'
... (2 Replies)
Hi all,
i am new to scripting. i need to write a code to detect begin and end of word that either begins or ends with t,th,d,dh,s,sh
i have a set of words in a file containg one word per line. let the filename be aaa.txt.
i have an another file bbb.txt which has two lines, just specifying the... (7 Replies)
Hi
I have written a script .The script runs properly if i write sql queries .But if i use PLSQL commands of BEGIN if end if , end ,then on running the script the comamds are getting printed on the prompt .
Ex :temp.sql
After connecting to the databse at the sql prompt i type... (1 Reply)
Hi All ,
I am newbie to linux shell scripting , below are the contents of my log file ,
i want the lines between a begin pattern and a end pattern
for an instance , my begin Pattern is "Transaction Begins for Usr"
and end pattern is "Transaction Ends for Usr" into another file
Sample file... (1 Reply)
Hi All,
test file
Begin Script Run at Thu Mar 14 09:24:16 PDT 2013
tst_accounts: ws zip: WS_out_20130313.tar.gz dat: test_20130313.dat count: 63574 loaded: xx pre-merge: xx post-merge: xx timestamp: Thu Mar 14 09:30:42 PDT 2013
tst_accounts: ws zip: WS_out_20130313.tar.gz dat: s_20130313.dat... (6 Replies)
I'm new to awk, trying to understand the basics.
I'm trying to reset the counter everytime the program gets a new file to check.
I figured in the BEGIN part it would work, but it doesn't.
#!/bin/awk -f
BEGIN {counter=0}
{
sum=0
for ( i=1; i<=NF;... (1 Reply)
Hello Friends ,
Please help to create script for compare and replace if not matches of set of lines .
* Primary*
Servername Server1
Location R201
Rack 4
*End Primary*
*Secondary*
Server Name Server1
IPAddress 10.24.30.10
Application Apache
*End of Secondary*
Above... (4 Replies)
I have a log file which lists groups and users in the following format
GROUP1
user1
user2
user3
GROUP2
user4
user5
user6
GROUP3
user7
user8
I need to change the format to:
user1|GROUP1
user2|GROUP1
user3|GROUP1
user4|GROUP2 (3 Replies)
I have this fileA
TEST FILE ABC
this file contains ABC;
TEST FILE DGHT this file contains DGHT;
TEST FILE 123
this file contains ABC,
this file contains DEF,
this file contains XYZ,
this file contains KLM
;
I want to have a fileZ that has only (begin search pattern for will be... (2 Replies)
Hello all,
How can I find out the start and end of the writing file in the directory or recording time for writing file?
I have a directory where small ~ 1*MB temporary files are written.
After the end of the record, they are retrieved and erased.
I can only find out that the files are... (4 Replies)
Discussion started by: mrAibo
4 Replies
LEARN ABOUT CENTOS
sd_journal_get_monotonic_usec
SD_JOURNAL_GET_REALTIME_USEC(3) sd_journal_get_realtime_usec SD_JOURNAL_GET_REALTIME_USEC(3)NAME
sd_journal_get_realtime_usec, sd_journal_get_monotonic_usec - Read timestamps from the current journal entry
SYNOPSIS
#include <systemd/sd-journal.h>
int sd_journal_get_realtime_usec(sd_journal* j, uint64_t* usec);
int sd_journal_get_monotonic_usec(sd_journal* j, uint64_t* usec, sd_id128_t* boot_id);
DESCRIPTION
sd_journal_get_realtime_usec() gets the realtime (wallclock) timestamp of the current journal entry. It takes two arguments: the journal
context object and a pointer to a 64-bit unsigned integer to store the timestamp in. The timestamp is in microseconds since the epoch, i.e.
CLOCK_REALTIME.
sd_journal_get_monotonic_usec() gets the monotonic timestamp of the current journal entry. It takes three arguments: the journal context
object, a pointer to a 64-bit unsigned integer to store the timestamp in, as well as a 128-bit ID buffer to store the boot ID of the
monotonic timestamp. The timestamp is in microseconds since boot-up of the specific boot, i.e. CLOCK_MONOTONIC. Since the monotonic clock
begins new with every reboot, it only defines a well-defined point in time when used together with an identifier identifying the boot. See
sd_id128_get_boot(3) for more information. If the boot ID parameter is passed NULL, the function will fail if the monotonic timestamp of
the current entry is not of the current system boot.
Note that these functions will not work before sd_journal_next(3) (or related call) has been called at least once, in order to position the
read pointer at a valid entry.
RETURN VALUE
sd_journal_get_realtime_usec() and sd_journal_get_monotonic_usec() returns 0 on success or a negative errno-style error code. If the boot
ID parameter was passed NULL and the monotonic timestamp of the current journal entry is not of the current system boot, -ESTALE is
returned by sd_journal_get_monotonic_usec().
NOTES
The sd_journal_get_realtime_usec() and sd_journal_get_monotonic_usec() interfaces are available as a shared library, which can be compiled
and linked to with the libsystemd-journal pkg-config(1) file.
SEE ALSO systemd(1), sd-journal(3), sd_journal_open(3), sd_journal_next(3), sd_journal_get_data(3), sd_id128_get_boot(3), clock_gettime(2),
sd_journal_get_cutoff_realtime_usec(3)systemd 208SD_JOURNAL_GET_REALTIME_USEC(3)
09-21-2011
