02-03-2009
Check weather a file is in use or not?
Hi,
Hi want to check weather a file is being used by using a command or java code or shell script.
So, can any body give me some idea..
Thanks
Buddhika
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear All
I want to do following task. Kindly suggest.
In my script every hour one file is genarated. say xyz.txt.
Now if this file contain some data then i want to do task A and if file is blank then i want to do nothing.
Kindly help me to do this.
regards
jaydeep (5 Replies)
Discussion started by: jaydeep_sadaria
5 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
Please tell me how to verify weather it is a ebcdic file or not . I checked with file commond but it is giving like International Language text.
Regards,
Chaitu (0 Replies)
Discussion started by: c_chaitanya
0 Replies
3. Shell Programming and Scripting
I think I can do this myself now, but I am always amazed by how people can do things cleaner and simpler than I end up doing...
Using cron, I want to save the image found at:
http://radar.weather.gov/ridge/Conus/RadarImg/centgrtlakes.gif
every 15 minutes to a local file , such as
... (1 Reply)
Discussion started by: brucewestfall
1 Replies
4. Shell Programming and Scripting
Hi everybody, I'm new to these forums and this is my first post. A couple days ago I was trying to find a simple script that would return an individual's local weather conditions using I.P. based geolocation. After many failed search attempts, I began my quest to create this for myself. I have to... (0 Replies)
Discussion started by: o0110o
0 Replies
5. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
6. Shell Programming and Scripting
#!/bin/sh
#Argentina Only :s
# This script requires curl and iconv, iconv is because they do not use Weather Service utf-8 ¬¬
# 87938 = Ushuaia
# 87934 = Rio Grande
# 87418 = Mendoza
# 87582 = Capital Federal
# 87692 = Mar del Plata
# 87480 = Rosario
# 87344 = Cordoba
# 87371 = Santa Fe
... (8 Replies)
Discussion started by: yamirokuay
8 Replies
7. Shell Programming and Scripting
Hi all,
i have a task to do with Python and because i'm a beginner on it i would like your help on this.
Create a python script that:
Every hour collect the Temperature (e.g. 29C) and Current Condition (e.g. Clear) from this website wunderground.com/global/stations/54511.html
Create a CSV... (0 Replies)
Discussion started by: ragaga123
0 Replies
8. Shell Programming and Scripting
Hey guys, I'm kinda stuck here.. I'm trying to write a script, which should start a short selftest via smartctl, for example
smartctl -t short /dev/sda
and after the test is finished I want it to write the new smartvalues in a logfile.
well... Now I need a return value for wether the... (1 Reply)
Discussion started by: phill971
1 Replies
LEARN ABOUT DEBIAN
git-check-attr
GIT-CHECK-ATTR(1) Git Manual GIT-CHECK-ATTR(1)
NAME
git-check-attr - Display gitattributes information
SYNOPSIS
git check-attr [-a | --all | attr...] [--] pathname...
git check-attr --stdin [-z] [-a | --all | attr...] < <list-of-paths>
DESCRIPTION
For every pathname, this command will list if each attribute is unspecified, set, or unset as a gitattribute on that pathname.
OPTIONS
-a, --all
List all attributes that are associated with the specified paths. If this option is used, then unspecified attributes will not be
included in the output.
--cached
Consider .gitattributes in the index only, ignoring the working tree.
--stdin
Read file names from stdin instead of from the command-line.
-z
Only meaningful with --stdin; paths are separated with a NUL character instead of a linefeed character.
--
Interpret all preceding arguments as attributes and all following arguments as path names.
If none of --stdin, --all, or -- is used, the first argument will be treated as an attribute and the rest of the arguments as pathnames.
OUTPUT
The output is of the form: <path> COLON SP <attribute> COLON SP <info> LF
<path> is the path of a file being queried, <attribute> is an attribute being queried and <info> can be either:
unspecified
when the attribute is not defined for the path.
unset
when the attribute is defined as false.
set
when the attribute is defined as true.
<value>
when a value has been assigned to the attribute.
EXAMPLES
In the examples, the following .gitattributes file is used:
*.java diff=java -crlf myAttr
NoMyAttr.java !myAttr
README caveat=unspecified
o Listing a single attribute:
$ git check-attr diff org/example/MyClass.java
org/example/MyClass.java: diff: java
o Listing multiple attributes for a file:
$ git check-attr crlf diff myAttr -- org/example/MyClass.java
org/example/MyClass.java: crlf: unset
org/example/MyClass.java: diff: java
org/example/MyClass.java: myAttr: set
o Listing all attributes for a file:
$ git check-attr --all -- org/example/MyClass.java
org/example/MyClass.java: diff: java
org/example/MyClass.java: myAttr: set
o Listing an attribute for multiple files:
$ git check-attr myAttr -- org/example/MyClass.java org/example/NoMyAttr.java
org/example/MyClass.java: myAttr: set
org/example/NoMyAttr.java: myAttr: unspecified
o Not all values are equally unambiguous:
$ git check-attr caveat README
README: caveat: unspecified
SEE ALSO
gitattributes(5).
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-CHECK-ATTR(1)