11-30-2007
how about
#!/bin/ksh
until [[ 1 -gt 2 ]]; do # infinite loop
status="found" # default to true
for i in file1 file2 file3; do
if [ ! -f $i ]; then
status="not found" # if one or more of the files doesn't exist set to false
fi
done
echo Files are ${status}.
sleep 5
done
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi, I have a list of filenames and I want to verify if they all exist. I know "if filename" would do the trick but how do I go about a list of files? thanks (3 Replies)
Discussion started by: mpang_
3 Replies
2. 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
3. UNIX for Dummies Questions & Answers
Hi,
- The first question I have concerns a very fundamental aspect of a unix OS. Specifically, does unix treat everything as a file (ie a directory is just a type of file)?
- The reason I ask is that I am trying to determine which BASH unary operator I would to use to determine whether or not... (1 Reply)
Discussion started by: msb65
1 Replies
4. Shell Programming and Scripting
Hi Forum.
I need a script to wait for all multiple trigger files to be present or else go to sleep for 10 seconds (Number of trigger files can vary). I tried to search on the forum but was not able to find a solution.
I found this code on this forum but it's not working as expected:
for... (6 Replies)
Discussion started by: pchang
6 Replies
5. Shell Programming and Scripting
Hello,
Can you please help me to see if log files exist in a directory?
I need to scan logs in different directories, so I am using an array to change dynamically.
I need help in the if test statement
dir=/logs/MSD
dir=/logs/UPD
countA=1
while (( countA <= ${#dir
} ))
do
cd ${dir}... (1 Reply)
Discussion started by: drbiloukos
1 Replies
6. Shell Programming and Scripting
Infile
Outfile (3 Replies)
Discussion started by: dvah
3 Replies
7. Shell Programming and Scripting
Hi,
I am checking for existence of files with the same extensions
#! /usr/bin/ksh
txtfiles = '*.txt'
if
then
cp ${dirpath}/${txtfiles} ${dir2path}
fi
I am getting the following error
line 5: [: too many arguments for the if check condition (4 Replies)
Discussion started by: chen.sara
4 Replies
8. Shell Programming and Scripting
Hi I am having a problem to verify existence of files. I need to know whether or not files in a folder that begins with a name.
For example all files that start with The_File_ *.
I was doing it this way, but gives me error.
if text -f /work/The_File_*
then
...
else
..
fi (5 Replies)
Discussion started by: Rodrih92
5 Replies
9. Shell Programming and Scripting
Hi,
I have two files
file1:
ALEX
DANY
GARY
TOM
MARY
HARRIS
file2:
ALEX 3
ALEX 5
ALEX 0
ALEX 1
ALEX 0
DANY 2 (2 Replies)
Discussion started by: Diya123
2 Replies
10. Shell Programming and Scripting
Hi
I have a requirement to check whether the files exists, then it will call other steps in shell script.
I did
ls *.csv|wc -l
if
then checking the count of the files should be more than 1 then it will call other steps.
I am getting the error that too many arguements as there n... (13 Replies)
Discussion started by: cnrj
13 Replies
MERGE(1) General Commands Manual MERGE(1)
NAME
merge - three-way file merge
SYNOPSIS
merge [ options ] file1 file2 file3
DESCRIPTION
merge incorporates all changes that lead from file2 to file3 into file1. The result ordinarily goes into file1. merge is useful for com-
bining separate changes to an original. Suppose file2 is the original, and both file1 and file3 are modifications of file2. Then merge
combines both changes.
A conflict occurs if both file1 and file3 have changes in a common segment of lines. If a conflict is found, merge normally outputs a
warning and brackets the conflict with <<<<<<< and >>>>>>> lines. A typical conflict will look like this:
<<<<<<< file A
lines in file A
=======
lines in file B
>>>>>>> file B
If there are conflicts, the user should edit the result and delete one of the alternatives.
OPTIONS
-A Output conflicts using the -A style of diff3(1), if supported by diff3. This merges all changes leading from file2 to file3 into
file1, and generates the most verbose output.
-E, -e These options specify conflict styles that generate less information than -A. See diff3(1) for details. The default is -E. With
-e, merge does not warn about conflicts.
-L label
This option may be given up to three times, and specifies labels to be used in place of the corresponding file names in conflict
reports. That is, merge -L x -L y -L z a b c generates output that looks like it came from files x, y and z instead of from files
a, b and c.
-p Send results to standard output instead of overwriting file1.
-q Quiet; do not warn about conflicts.
-V Print RCS's version number.
DIAGNOSTICS
Exit status is 0 for no conflicts, 1 for some conflicts, 2 for trouble.
IDENTIFICATION
Author: Walter F. Tichy.
Manual Page Revision: 5.8.1; Release Date: 2012-06-06.
Copyright (C) 2010-2012 Thien-Thi Nguyen.
Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995 Paul Eggert.
Copyright (C) 1982, 1988, 1989 Walter F. Tichy.
SEE ALSO
diff3(1), diff(1), rcsmerge(1), co(1).
BUGS
It normally does not make sense to merge binary files as if they were text, but merge tries to do it anyway.
GNU RCS 5.8.1 2012-06-06 MERGE(1)