09-30-2008
Checking existence of file using file pattern
Hi Experts
,
I need to check the existense of file using patterns.How can i do it?
Ex:
if my current directory has a number of files of pattern (ins_*),
i need to check the existense of atleast one file.
pls reply me.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
My requirement was to check the existence of a file having a specified pattern.The way i tried to achieve this was
if ; then
echo "File found"
fi
an example file having this pattern was 'ilvs_trace01.0124'.
it will vary... (3 Replies)
Discussion started by: DILEEP410
3 Replies
2. Shell Programming and Scripting
Hi,
I am trying to check for the existence of a file using the 'test' and the file existence options.
When trying to check for a file with a space in between e.g 'Team List', it gives the following error.
learn1: line 3: test: `Team: binary operator expected
I am pasting my code below as... (7 Replies)
Discussion started by: igandu
7 Replies
3. Shell Programming and Scripting
Hi,
I want to check multiple files exist or not in a single if statement in korn Shell:confused:.
Please help me
Thanks (1 Reply)
Discussion started by: lathish
1 Replies
4. Shell Programming and Scripting
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)
Discussion started by: lathish
2 Replies
5. Shell Programming and Scripting
Hi,
I am trying to check the existence of a file, from a list of possible filenames:
status-A
status-B
status-C
before retrieving the last modified datetime using ls, I want to check it exists or ls will throw an error.
So I have tried this:
if ; then
ls status-*
fi
But the if... (3 Replies)
Discussion started by: LostInTheWoods
3 Replies
6. Shell Programming and Scripting
Hi
Can any body say me the reason for below error
ssh -o 'StrictHostKeyChecking no' user@client ' && print "1"'
I am getting error as "Missing ]":wall: (6 Replies)
Discussion started by: ramesh12621
6 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am a SAP- ABAP programer , i have only little knowledge of Unix.
My issue is i have a list of files which are in internal table.
I want to create a script which consist of all these files and in one go i can check in the unix server about there existance and there file size.
Can... (2 Replies)
Discussion started by: amitkumar.b2
2 Replies
8. Shell Programming and Scripting
Hi,
I need to check whether a particular file exists ot not using awk.
Can anyone help me please?
For Example:script that i am using:
awk '{filename =$NF;
rc=(system("test -r filename")) print $rc;}' "$1"
is not working.
Here I am passing a text file as input whose last word contains a... (6 Replies)
Discussion started by: manish007
6 Replies
9. Shell Programming and Scripting
Hi am trying to write a script which find the existence of a file from a find command output and perform a task if the file exists. Help me out with the correct syntax . Am trying with the following one but unable to get the output.
if
then <some tasks>
else
echo "file not exists"
fi (5 Replies)
Discussion started by: rogerben
5 Replies
10. Shell Programming and Scripting
Hi,
I have written a script to validate the data file by referreing to the configurtion file. And moving the validated good records and bad records into HDFS.
Suppose after 15 mins if i receive one more data fie,then after validation the good and bad records shold be stored in hadoop with the... (8 Replies)
Discussion started by: shree11
8 Replies
LEARN ABOUT LINUX
git-check-ignore
GIT-CHECK-IGNORE(1) Git Manual GIT-CHECK-IGNORE(1)
NAME
git-check-ignore - Debug gitignore / exclude files
SYNOPSIS
git check-ignore [options] pathname...
git check-ignore [options] --stdin < <list-of-paths>
DESCRIPTION
For each pathname given via the command-line or from a file via --stdin, show the pattern from .gitignore (or other input files to the
exclude mechanism) that decides if the pathname is excluded or included. Later patterns within a file take precedence over earlier ones.
OPTIONS
-q, --quiet
Don't output anything, just set exit status. This is only valid with a single pathname.
-v, --verbose
Also output details about the matching pattern (if any) for each given pathname.
--stdin
Read file names from stdin instead of from the command-line.
-z
The output format is modified to be machine-parseable (see below). If --stdin is also given, input paths are separated with a NUL
character instead of a linefeed character.
-n, --non-matching
Show given paths which don't match any pattern. This only makes sense when --verbose is enabled, otherwise it would not be possible to
distinguish between paths which match a pattern and those which don't.
--no-index
Don't look in the index when undertaking the checks. This can be used to debug why a path became tracked by e.g. git add . and was
not ignored by the rules as expected by the user or when developing patterns including negation to match a path previously added with
git add -f.
OUTPUT
By default, any of the given pathnames which match an ignore pattern will be output, one per line. If no pattern matches a given path,
nothing will be output for that path; this means that path will not be ignored.
If --verbose is specified, the output is a series of lines of the form:
<source> <COLON> <linenum> <COLON> <pattern> <HT> <pathname>
<pathname> is the path of a file being queried, <pattern> is the matching pattern, <source> is the pattern's source file, and <linenum> is
the line number of the pattern within that source. If the pattern contained a ! prefix or / suffix, it will be preserved in the output.
<source> will be an absolute path when referring to the file configured by core.excludesfile, or relative to the repository root when
referring to .git/info/exclude or a per-directory exclude file.
If -z is specified, the pathnames in the output are delimited by the null character; if --verbose is also specified then null characters
are also used instead of colons and hard tabs:
<source> <NULL> <linenum> <NULL> <pattern> <NULL> <pathname> <NULL>
If -n or --non-matching are specified, non-matching pathnames will also be output, in which case all fields in each output record except
for <pathname> will be empty. This can be useful when running non-interactively, so that files can be incrementally streamed to STDIN of a
long-running check-ignore process, and for each of these files, STDOUT will indicate whether that file matched a pattern or not. (Without
this option, it would be impossible to tell whether the absence of output for a given file meant that it didn't match any pattern, or that
the output hadn't been generated yet.)
Buffering happens as documented under the GIT_FLUSH option in git(1). The caller is responsible for avoiding deadlocks caused by
overfilling an input buffer or reading from an empty output buffer.
EXIT STATUS
0
One or more of the provided paths is ignored.
1
None of the provided paths are ignored.
128
A fatal error was encountered.
SEE ALSO
gitignore(5) gitconfig(5) git-ls-files(1)
GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-CHECK-IGNORE(1)