|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
check file is there not in linux using if statement
Post 302313011 by nskbalu on Monday 4th of May 2009 11:14:12 AM
05-04-2009
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
this statement "Be sure to have /usr/bin before /usr/local/bin in your $PATH" is because, if u have any files in bin directory, /usr/local/bin will be the first place to look at instead of /usr/bin. BUT, /usr/local/bin has one more descending directory to go , therefore /usr/bin has to come before... (2 Replies)
Discussion started by: yls177
2 Replies
2. Shell Programming and Scripting
Hi,
I was wondering if it possible to get the path of a variable and compare that to something. Basically I want to write a script that checks if my $JAVA_HOME is correct and if not then it sets it. So far I have...
if ]
then
export JAVA_HOME='/pathhere'
echo JAVA_HOME='/pathhere'
fi
... (6 Replies)
Discussion started by: eltinator
6 Replies
3. Shell Programming and Scripting
Hi,
I'm trying to write a bit of code that will check if a file exists and then archives the file
Im trying to use the following if statement without success..
if
then
mv filename archive/filename
else
echo "no filename exists"
fi
Should the file name be... (3 Replies)
Discussion started by: Jazmania
3 Replies
4. Shell Programming and Scripting
Hi,
Am trying to execute certain commands if the condition satisfied, but i feel i am making some mistakes in the usage of if statement
here is the code
#!/bin/ksh
SIZE=$(ls -ltr /aemu/ws/DN.txt | tr -s ' ' | cut -d ' ' -f 5)
filename=`TZ=CST+24 date +%Y%m%d`
ZERO=0
if
then
cp... (5 Replies)
Discussion started by: aemunathan
5 Replies
5. Shell Programming and Scripting
Hi All,
If i run below copy command, it works absolutely fine,
/opt/csw/bin/scp axetlxyz01:/opt/data/test/QURIES* ./input
I want to make the above line better, by adding an IF statement, want to check if there is any file exists with name QURIES*.* then i need to copy that.
if
... (7 Replies)
Discussion started by: rkrgarlapati
7 Replies
6. Shell Programming and Scripting
This is what I have so far
grep -lir "some text" *
I need to check all files on the system for this text, if the text is found I need to change the file permissions so only ROOT has read and write access.
How can this be done? (3 Replies)
Discussion started by: mapleleafs89
3 Replies
7. Shell Programming and Scripting
Hi All,
I have a simple problem .
I am pulling the file from a remote server througha simple file transfer protocal (ftp ).
But I wanted to check before pulling the file ,whether the file is being written or in use by some other process and if so i dont want to pull the file and wait for... (1 Reply)
Discussion started by: ptappeta
1 Replies
8. Shell Programming and Scripting
I wish to check two conditions inside the if statement
Condition 1: The two file contents should be identical // using cmp command for this.
Condition 2: The two filenames should NOT be the same.
This is what i did in vain.
if ]; then
where entry1 and entry2 are
ls *.txt | while... (7 Replies)
Discussion started by: mohtashims
7 Replies
9. UNIX for Beginners Questions & Answers
Hello Guys,
I am trying scp few file within if statement, but getting error, can someone please help to understand, what mistake I am making ?
if && ] ;
then
echo " Files transferred to Log servers successfully. "
else
echo " One or more file transfer failed over... (10 Replies)
Discussion started by: UnknownGuy
10 Replies
10. UNIX for Beginners Questions & Answers
Hi,
I am running a shell script that has to verify a password with an if statement. The password has an @ in it. I am having problems getting the if statement to test for the password. The @ causes problem. I tried the standard backslash escape but it did not work for me.
How can I do it?
I... (2 Replies)
Discussion started by: mojoman
2 Replies
LEARN ABOUT OPENSOLARIS
settime
touch(1) User Commands touch(1) NAME
touch, settime - change file access and modification times SYNOPSIS
touch [-acm] [-r ref_file | -t time] file... touch [-acm] [date_time] file... settime [-f ref_file] [date_time] file... DESCRIPTION
The touch utility sets the access and modification times of each file. The file operand is created if it does not already exist. The time used can be specified by -t time, by the corresponding time fields of the file referenced by -r ref_file, or by the date_time op- erand. If none of these are specified, touch uses the current time (the value returned by the time(2) function). If neither the -a nor -m options are specified, touch updates both the modification and access times. A user with write access to a file, but who is not the owner of the file or a super-user, can change the modification and access times of that file only to the current time. Attempts to set a specific time with touch will result in an error. The settime utility is equivalent to touch -c [date_time] file. OPTIONS
The following options are supported in the touch and settime utilities: touch The following options are supported for the touch utility: -a Changes the access time of file. Does not change the modification time unless -m is also specified. -c Does not create a specified file if it does not exist. Does not write any diagnostic messages concerning this condition. -m Changes the modification time of file. Does not change the access time unless -a is also specified. -r ref_file Uses the corresponding times of the file named by ref_file instead of the current time. -t time Uses the specified time instead of the current time. time will be a decimal number of the form: [[CC]YY]MMDDhhmm[.SS] where each two digits represent the following: MM The month of the year [01-12]. DD The day of the month [01-31]. hh The hour of the day [00-23]. mm The minute of the hour [00-59]. CC The first two digits of the year. YY The second two digits of the year. SS The second of the minute [00-61]. Both CC and YY are optional. If neither is given, the current year will be assumed. If YY is specified, but CC is not, CC will be derived as follows: +-----------------------------------------------------------+ | If YY is: CC becomes: | +-----------------------------------------------------------+ |69-99 19 | |00-38 20 | |39-68 ERROR | +-----------------------------------------------------------+ The resulting time will be affected by the value of the TZ environment variable. If the resulting time value precedes the Epoch, touch will exit immediately with an error status. The range of valid times is the Epoch to January 18, 2038. The range for SS is [00-61] rather than [00-59] because of leap seconds. If SS is 60 or 61, and the resulting time, as affected by the TZ environment variable, does not refer to a leap second, the resulting time will be one or two seconds after a time where SS is 59. If SS is not given, it is assumed to be 0. settime The following option is supported for the settime utility: -f ref_file Uses the corresponding times of the file named by ref_file instead of the current time. OPERANDS
The following operands are supported for the touch and settime utilities: file A path name of a file whose times are to be modified. date_time Uses the specified date_time instead of the current time. This operand is a decimal number of the form: MMDDhhmm[YY] where each two digits represent the following: MM The month of the year [01-12]. DD The day of the month [01-31]. hh The hour of the day [00-23]. mm The minute of the hour [00-59]. YY The second two digits of the year. YY is optional. If it is omitted, the current year will be assumed. If YY is specified, the year will be derived as follows: +-----------------------------------------------------------+ | YY Corresponding Year | |69-99 1969-1999 | |00-38 2000-2038 | |39-68 ERROR | +-----------------------------------------------------------+ If no -r option is specified, no -t option is specified, at least two operands are specified, and the first operand is an eight- or ten-digit decimal integer, the first operand will be assumed to be a date_time operand. Otherwise, the first operand will be assumed to be a file operand. USAGE
See largefile(5) for the description of the behavior of touch when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes). When existing file access and modification times cannot be determined (which will occur if a call to stat(2) fails), both times can be changed to known values by settime and utime(2). However, in this case, touch -a (without -m) and touch -m (without -a) will fail because the unchanged time cannot be preserved. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of touch: LANG, LC_ALL, LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH. TZ Determine the timezone to be used for interpreting the time option-argument or the date_time operand. EXIT STATUS
The following exit values are returned: 0 The touch utility executed successfully and all requested changes were made. >0 An error occurred. The touch utility returned the number of files for which the times could not be successfully modified. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ SEE ALSO
stat(2), time(2), utime(2), attributes(5), environ(5), largefile(5), standards(5) NOTES
Users familiar with the BSD environment will find that for the touch utility, the -f option is accepted but ignored. The -f option is unnecessary because touch will succeed for all files owned by the user regardless of the permissions on the files. SunOS 5.11 9 Sep 2008 touch(1)