07-19-2014
Why would that break old scripts ?
-a and
-o will most likely remain supported by the implementations ...
Obsolescent means that is has become outdated and its usage is discouraged, for the reasons given and there is the intention to remove it from the standard..
Quote:
Q15. Does removal of obsolescent utility syntax mean that implementations supporting usages of head -5 file, tail -5 file, tail -l file are no longer allowed?
No, in general the intent of removing the obsolescent forms of the utility synopses was not to disallow them to be supported by implementations but to downgrade the status of their use in applications from conforming application using an obsolescent feature to non-conforming application. In general it is allowed for utilities to have extensions that violate the utility syntax guidelines so long as the forms defined in the standard that are required to follow the utility syntax guidelines do so. The cases cited fit the case. The Austin Group has more general cases under review at the present time.
POSIX.1 FAQ
---
Quote:
Originally Posted by
techy1
Strange. If i dont use the -o it just doesnt work. Its been a really long time since i had to use -o i forgot about that option
What version of ksh are you using on what OS? Even though older implementations are not POSIX compliant, they should support that syntax..
Last edited by Scrutinizer; 07-19-2014 at 08:41 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I am having trouble with the syntax with a conditional statement in a BASH script involving multiple conditions. Any suggestions would be greatly appreciated!
if ; then
array=("${array}" "$dnNum" )
fi
i receive this error:
./testscript: ' (4 Replies)
Discussion started by: grandtheftander
4 Replies
2. Shell Programming and Scripting
Guys, Im trying to have a script that evaluates multiple conditions :
test.sh:
if
then
echo "host $1"
else
if
then
echo "host $1"
else
echo $1 not valid
exit 1
fi
when I do
./test.sh brazil1
I get: (4 Replies)
Discussion started by: bashshadow1979
4 Replies
3. Shell Programming and Scripting
Hi All,
I am new to shell scripting.
Can any one say what is wrong in this if statement, that uses multiple conditions
if
then
***************
else
if ( -z $pcs && "$night_time_calc" > "$night_time" )
then
********************************
... (4 Replies)
Discussion started by: ssenthilkumar
4 Replies
4. Shell Programming and Scripting
how can i specify more than 1 consition in the following AWK statament??
i.e. if $2 is ABCD and $3 is MNOP and $4 is KLPM
similarly for OR
#!/bin/ksh
awk -F '' ' $2 == "ABCD" { print $2, $3;}' file.xml (2 Replies)
Discussion started by: skyineyes
2 Replies
5. Shell Programming and Scripting
Hi,
When i use the below code snippet in my shell script OFC_10.sh:
if
then
echo "Success"
exit 2
elif
then
echo "Failure"
exit 6
I get the error message:
./OFC_10.sh: line 41: '
./OFC_10.sh: line 45: '
Line 41 is the line where If loop starts and line 45 is... (2 Replies)
Discussion started by: shrutihardas
2 Replies
6. UNIX for Dummies Questions & Answers
Deal Experts
I am working on a script to find a date which is 7 days older and follwoing is my approach
#!/bin/sh
Yr=`date +"%Y"`
Mn=`date +"%m"`
Md=28
Da=`date +"%d"`
echo $Yr
echo $Mn
echo $Da
var1=$Yr$Mn$Da
echo "before" $var1
if expr $Da > 7
then Da=`expr $Da - 7`... (3 Replies)
Discussion started by: sweetnsourabh
3 Replies
7. UNIX for Dummies Questions & Answers
Hello Unix-Forums!
It has been a long time since my last post, but finally I've got a new question:
I know in case you can use multiple patterns by
case $var in
a|b|c|ab)
and so on.
But how would I place an OR between
if ]
then
...
if ]
then
...
I want to execute the "..." if... (3 Replies)
Discussion started by: intelinside
3 Replies
8. Shell Programming and Scripting
Fellas,
Am new to unix os/ and here the situation , I am trying to write multiple condition statement inside if but it throws me a error
here is my piece of code ,
if ] && ] && ]
then
commands
fi
error : line 15 : `
can someone please advise me how to fix it
Please use... (7 Replies)
Discussion started by: xeccc5z
7 Replies
9. UNIX for Beginners Questions & Answers
Hi Gurus,
Is there a way we can set a logic for this problem ?
The input file looks like below;
1 15 17
2 8 12
3 18 24
4 21 23
5 2 4
6 11 25
So, I would like to print for any row of the input file where the range of value between $2 to $3 lies within the min and max values of Min=10... (2 Replies)
Discussion started by: Indra2011
2 Replies
10. UNIX for Beginners Questions & Answers
I am analyzing one of the scripts written by another person.script is having multiple if conditions and everything are nested.The code is not formatted properly.Is there any way to identify in Unix to identify begin and end of a particular if block? (6 Replies)
Discussion started by: vamsi.valiveti
6 Replies
HEAD(1P) POSIX Programmer's Manual HEAD(1P)
PROLOG
This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the correspond-
ing Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.
NAME
head - copy the first part of files
SYNOPSIS
head [-n number][file...]
DESCRIPTION
The head utility shall copy its input files to the standard output, ending the output for each file at a designated point.
Copying shall end at the point in each input file indicated by the -n number option. The option-argument number shall be counted in units
of lines.
OPTIONS
The head utility shall conform to the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.
The following option shall be supported:
-n number
The first number lines of each input file shall be copied to standard output. The application shall ensure that the number option-
argument is a positive decimal integer.
When a file contains less than number lines, it shall be copied to standard output in its entirety. This shall not be an error.
If no options are specified, head shall act as if -n 10 had been specified.
OPERANDS
The following operand shall be supported:
file A pathname of an input file. If no file operands are specified, the standard input shall be used.
STDIN
The standard input shall be used only if no file operands are specified. See the INPUT FILES section.
INPUT FILES
Input files shall be text files, but the line length is not restricted to {LINE_MAX} bytes.
ENVIRONMENT VARIABLES
The following environment variables shall affect the execution of head:
LANG Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of
IEEE Std 1003.1-2001, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to
determine the values of locale categories.)
LC_ALL If set to a non-empty string value, override the values of all the other internationalization variables.
LC_CTYPE
Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to
multi-byte characters in arguments and input files).
LC_MESSAGES
Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
NLSPATH
Determine the location of message catalogs for the processing of LC_MESSAGES .
ASYNCHRONOUS EVENTS
Default.
STDOUT
The standard output shall contain designated portions of the input files.
If multiple file operands are specified, head shall precede the output for each with the header:
"
==> %s <==
", <pathname>
except that the first header written shall not include the initial <newline>.
STDERR
The standard error shall be used only for diagnostic messages.
OUTPUT FILES
None.
EXTENDED DESCRIPTION
None.
EXIT STATUS
The following exit values shall be returned:
0 Successful completion.
>0 An error occurred.
CONSEQUENCES OF ERRORS
Default.
The following sections are informative.
APPLICATION USAGE
The obsolescent - number form is withdrawn in this version. Applications should use the -n number option.
EXAMPLES
To write the first ten lines of all files (except those with a leading period) in the directory:
head *
RATIONALE
Although it is possible to simulate head with sed 10q for a single file, the standard developers decided that the popularity of head on
historical BSD systems warranted its inclusion alongside tail.
This standard version of head follows the Utility Syntax Guidelines. The -n option was added to this new interface so that head and tail
would be more logically related.
There is no -c option (as there is in tail) because it is not historical practice and because other utilities in this volume of
IEEE Std 1003.1-2001 provide similar functionality.
FUTURE DIRECTIONS
None.
SEE ALSO
sed, tail
COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol-
ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE
and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained
online at http://www.opengroup.org/unix/online.html .
IEEE
/The Open Group 2003 HEAD(1P)