Sponsored Content
Top Forums Shell Programming and Scripting -s option stands for ? *Urgent Post 302284627 by sunpraveen on Friday 6th of February 2009 01:38:58 AM
Old 02-06-2009
Kunal,

For filenames the options are:

-r true if it exists and is readable
-w
true if it exists and is writable
-x
true if it exists and is executable
-f
true if it exists and is a regular file (or for csh, exists and is not a directory)
-d
true if it exists and is a directory
-h
or -L true if it exists and is a symbolic link
-c
true if it exists and is a character special file (i.e. the special device is accessed
one character at a time)
-b
true if it exists and is a block special file (i.e. the device is accessed in blocks
of data)
-p
true if it exists and is a named pipe (fifo)
-u
true if it exists and is setuid (i.e. has the set-user-id bit set, s or S in the third
bit)
-g
true if it exists and is setgid (i.e. has the set-group-id bit set, s or S in the sixth
bit)
-k
true if it exists and the sticky bit is set (a t in bit 9)
-s true if it exists and is greater than zero in size

HTH, Smilie

Regards,

Praveen
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

file extension stands for mksys?

hi, what does this mksys stands for in unix? seems like its something to do with the os. i am using aix (1 Reply)
Discussion started by: yls177
1 Replies

2. Shell Programming and Scripting

option followed by : taking next option if argument missing with getopts

Hi all, I am parsing command line options using getopts. The problem is that mandatory argument options following ":" is taking next option as argument if it is not followed by any argument. Below is the script: while getopts :hd:t:s:l:p:f: opt do case "$opt" in -h|-\?)... (2 Replies)
Discussion started by: gurukottur
2 Replies

3. UNIX for Dummies Questions & Answers

Urgent -Please help me 'mail' option not working

Hi , I have already posted a post regarding this, but i didn't get my problem solve, so some body help me as it was urgent for me, my mail option is not working, when i send a mail, it is strucking in /var/spool/mqueue folder. and i am getting struck there itself, i see below two files are... (1 Reply)
Discussion started by: mars_girish9
1 Replies

4. Shell Programming and Scripting

"cc +DS1.1 +DA1.1" what does this option stands for?

Hi all cc +DA1.1 +DS1.1 -o /tmp/testapis /tmp/file.c While compiling the temp.c file i encounter the above line in my shell script. I would like to know what the options +DA1.1 and +DS1.1 is used for. After googling i found that we need to use it on PA RISC machines but a more detailed... (0 Replies)
Discussion started by: gurubarancse
0 Replies

5. Red Hat

In ypserv what yp stands for?

Hi can any one please tell what yp stands for in ypserv daemon (1 Reply)
Discussion started by: Gopi Krishna P
1 Replies

6. Shell Programming and Scripting

recently introduced to the newer option for find...does an older option exist?

To find all the files in your home directory that have been edited in some way since the last tar file, use this command: find . -newer backup.tar.gz Is anyone familiar with an older solution? looking to identify files older then 15mins across several directories. thanks, manny (2 Replies)
Discussion started by: mr_manny
2 Replies

7. UNIX for Dummies Questions & Answers

what does -e stands for

Below is a part of a script - if I know -eq means equals in a n if statement but what does this -e means here ? Please help. Thanks (2 Replies)
Discussion started by: csrohit
2 Replies

8. Solaris

Unrecognized option: sparc-sun-Solaris2.10/bin/as: unrecognized option `-m32'

Hi, I installed some packages required by an app built with python. But when I try python setup.py install, I get the following error: /opt/csw/lib/gcc/sparc-sun-solaris2.10/5.2.0/../../../../sparc-sun-solaris2.10/bin/as: unrecognized option `-m32' Could anyone tell me what's wrong... (4 Replies)
Discussion started by: Kimkun
4 Replies

9. Shell Programming and Scripting

URGENT Reading a file and assessing the syntax shell script URGENT

I am trying to write a shell script which takes an input file as an arguement in the terminal e.g. bash shellscriptname.sh input.txt. I would like for the file to be read line by line each time checking if the .txt file contains certain words or letters(validating the syntax). If the line being... (1 Reply)
Discussion started by: Gurdza32
1 Replies
doctools_lang_syntax(n) 					Documentation tools					   doctools_lang_syntax(n)

__________________________________________________________________________________________________________________________________________________

NAME
doctools_lang_syntax - doctools language syntax DESCRIPTION
This document contains the formal specification of the syntax of the doctools markup language, version 1 in Backus-Naur-Form. This document is intended to be a reference, complementing the doctools language command reference. A beginner should read the much more informally written doctools language introduction first before trying to understand either this document or the command reference. FUNDAMENTALS
In the broadest terms possible the doctools markup language is LaTeX-like, instead of like SGML and similar languages. A document written in this language consists primarily of text, with markup commands embedded into it. Each markup command is a just Tcl command surrounded by a matching pair of [ and ]. Which commands are available, and their arguments, i.e. syntax is specified in the doctools language command reference. In this document we specify first the lexeme, and then the syntax, i.e. how we can mix text and markup commands with each other. LEXICAL DEFINITIONS
In the syntax rules listed in the next section [1] <TEXT> stands for all text except markup commands. [2] Any XXX stands for the markup command [xxx] including its arguments. Each markup command is a Tcl command surrounded by a matching pair of [ and ]. Inside of these delimiters the usual rules for a Tcl command apply with regard to word quotation, nested commands, continuation lines, etc. [3] <WHITE> stands for all text consisting only of spaces, newlines, tabulators and the comment markup command. SYNTAX
The rules listed here specify only the syntax of doctools documents. The lexical level of the language was covered in the previous section. Regarding the syntax of the (E)BNF itself [1] The construct { X } stands for zero or more occurrences of X. [2] The construct [ X ] stands for zero or one occurrence of X. [3] The construct LIST_BEGIN<X> stands for the markup command list_begin with X as its type argument. The syntax: manpage = defs MANPAGE_BEGIN header DESCRIPTION body MANPAGE_END { <WHITE> } defs = { INCLUDE | VSET | <WHITE> } header = { TITLEDESC | MODDESC | COPYRIGHT | REQUIRE | defs | xref } xref = KEYWORDS | SEE_ALSO | CATEGORY body = paras { SECTION sbody } sbody = paras { SUBSECTION ssbody } ssbody = paras paras = tblock { (PARA | NL) tblock } tblock = { <TEXT> | defs | markup | xref | an_example | a_list } markup = ARG | CLASS | CMD | CONST | EMPH | FILE | FUN | LB | METHOD | NAMESPACE | OPT | OPTION | PACKAGE | RB | SECTREF | STRONG | SYSCMD | TERM | TYPE | URI | USAGE | VAR | WIDGET example = EXAMPLE | EXAMPLE_BEGIN extext EXAMPLE_END extext = { <TEXT> | defs | markup } a_list = LIST_BEGIN<arguments> argd_list LIST_END | LIST_BEGIN<commands> cmdd_list LIST_END | LIST_BEGIN<definitions> def_list LIST_END | LIST_BEGIN<enumerated> enum_list LIST_END | LIST_BEGIN<itemized> item_list LIST_END | LIST_BEGIN<options> optd_list LIST_END | LIST_BEGIN<tkoptions> tkoptd_list LIST_END argd_list = [ <WHITE> ] { ARG_DEF paras } cmdd_list = [ <WHITE> ] { CMD_DEF paras } def_list = [ <WHITE> ] { (DEF|CALL) paras } enum_list = [ <WHITE> ] { ENUM paras } item_list = [ <WHITE> ] { ITEM paras } optd_list = [ <WHITE> ] { OPT_DEF paras } tkoptd_list = [ <WHITE> ] { TKOPTION_DEF paras } BUGS, IDEAS, FEEDBACK This document, will undoubtedly contain bugs and other problems. Please report such in the category doctools of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have. SEE ALSO
doctools_intro, doctools_lang_cmdref, doctools_lang_faq, doctools_lang_intro KEYWORDS
doctools commands, doctools language, doctools markup, doctools syntax, markup, semantic markup COPYRIGHT
Copyright (c) 2007 Andreas Kupries <andreas_kupries@users.sourceforge.net> doctools 1.0 doctools_lang_syntax(n)
All times are GMT -4. The time now is 09:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy