I have the following report (report.txt) file (see attached).
I would like to check the file and if the field is error, then showing error message at output.
1. In the report, 1st, 2st and 3nd line can be ignore to check
2. start to check line 4 (each field use "," to split
- 1st field should be 5 digits (0-9)
- 2nd field should be A-Z
- 3rd field should be 5 digits (0-9)
- 4th field should be one char (Y or N)
- 5th field should be 00:00 to 99:99 or 0:00 to 9:99
- 6th field should be number or with "."
and so on....(i can do it by myself if you can provide above sample for me)
- until last two field, should be 3 char (A-Z)
3. At the end of the report, the line should be "*** End of Report *** ,,,,,,,,,,,,,,,,,,,,,,,,"
If any error for each field, just show the line number is ok for me.
Hi,
I'm currently trying to write a script that checks a log file for certain errors. Once checked it then records the filesize in another file. All this is fine, my problem is that the next time I do my error check I only want to check from previously recorded filesize to the end of file. I'm... (2 Replies)
I want to check the files in particular directory are more that 0 Bytes i.e, Non zero byte file. The script should print a msg if all the files in that directory are empty( 0 Byte). (2 Replies)
Hi All,
I am very new to Shell scripting...
I got a requirement.
I will have few text files(data files) in a particular directory. they will be with .txt extension. With same name, but with a different extension control files also will be there. For example, Sample_20081001.txt is the data... (4 Replies)
Hi All,
I am new to unix scripting, please help me in completing this exercise,
I have a scenario as follows,
1. i have a text file(snapshot.txt) consisting of directory names, and file
size separated by comma as shown below:
snapshot.txt data:
... (1 Reply)
All,
Is there a way to keep checking for a file over and over again in the same script for an interval of time?
Ie
If {
mail -user
continue checking until file arrives
file arrives
tasks
exit
I don't want the script to run each time and email the user each time a file... (4 Replies)
Hi,
I have 9 files which are generated dynamically & if there is a some condition which doesn't meet the criteria then file is not created or is of zero size.
so further i am unable to consolidate the files based on following code 1
awk -F, -v ptime="201407" 'FNR==1... (3 Replies)
HI Guys,
I have some 8 files with different name and extensions. I need to check if they are present in a specific folder or not and also want that script to show me which all are not present. I can write if condition for each file but from a developer perspective , i feel that is not a good... (3 Replies)
Hello,
I'm looking to check only the first line of a file to see if it is a format string, like
# -*- coding: utf-8; mode: tcl; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -\*- vim:fenc=utf-8:ft=tcl:et:sw=2:ts=2:sts=2if the first line is anything else, insert the above string.
I'd... (3 Replies)
hi all,
trying this using shell/bash with sed/awk/grep
I have two files, one containing one column, the other containing multiple columns (comma delimited).
file1.txt
abc12345
def12345
ghi54321
...
file2.txt
abc1,text1,texta
abc,text2,textb
def123,text3,textc
gh,text4,textd... (6 Replies)
Discussion started by: shogun1970
6 Replies
LEARN ABOUT DEBIAN
gd_eof
gd_eof(3) GETDATA gd_eof(3)NAME
gd_eof -- report the number of samples in a dirfile field
SYNOPSIS
#include <getdata.h>
off_t gd_eof(DIRFILE *dirfile, const char *field_code);
DESCRIPTION
The gd_eof() function queries a dirfile(5) database specified by dirfile and returns the sample number of the end-of-field marker for the
vector field given by field_code. This is effectively the total number of samples available for the field, including any frame offset.
The caller should not assume that this is equivalent (when accounting for the samples-per-frame of the indicated field) to the number of
frames in the database returned by gd_nframes(3), nor even that the end-of-field marker falls on a frame boundary.
For a RAW field, the end-of-field marker occurs immediately after the last datum in the data file associated with the field. For other
field types, the end-of-field marker is equivalent to the end-of-field marker closest to the start of the dirfile of any of the field in-
puts. The special field INDEX has no end-of-field marker.
The end-of-field marker for a field containing no data is in the same location as, or before, its beginning-of-field marker (see
gd_bof(3)). For a RAW field, the difference between the locations of the beginning- and end-of-field markers indicates the number of sam-
ples of data actually stored on disk.
The dirfile argument must point to a valid DIRFILE object previously created by a call to gd_open(3).
RETURN VALUE
Upon successful completion, gd_eof() returns the sample number of the end-of-field marker for the indicated field. On error, it returns -1
and sets the dirfile error to a non-zero error value. Possible error values are:
GD_E_BAD_CODE
The field specified by field_code or one of the fields it uses as input was not found in the database.
GD_E_BAD_DIRFILE
The supplied dirfile was invalid.
GD_E_BAD_FIELD_TYPE
The location of the non-existent end-of-field marker for the special field INDEX was requested, possibly as a result of the field
specified by field_code using INDEX as one of its inputs.
GD_E_BAD_REPR
The representation suffix specified in field_code, or in one of its inputs was not recognised.
GD_E_DIMENSION
A scalar field was found where a vector field was expected in the definition of field_code or one of its inputs, or else field_code
itself specified a scalar field.
GD_E_RAW_IO
An attempt to stat(2) the file associated with the field, or one of its input fields, failed.
GD_E_RECURSE_LEVEL
Too many levels of recursion were encountered while trying to resolve field_code. This usually indicates a circular dependency in
field specification in the dirfile.
GD_E_UNKNOWN_ENCODING
The size of the decoded data file associated with the specified field or one of its inputs could not be determined, because its en-
coding scheme was not understood.
GD_E_UNSUPPORTED
The size of the decoded data file associated with the specified field or one of its inputs could not be determined, because its en-
coding scheme was not supported.
The dirfile error may be retrieved by calling gd_error(3). A descriptive error string for the last error encountered can be obtained from
a call to gd_error_string(3).
SEE ALSO dirfile(5), dirfile-encoding(5), gd_open(3), gd_bof(3), gd_error(3), gd_error_string(3), gd_nframes(3)Version 0.7.0 15 October 2010 gd_eof(3)