Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: POSIX compliance...
Operating Systems OS X (Apple) POSIX compliance... Post 302976886 by Don Cragun on Thursday 7th of July 2016 02:24:13 PM
Old 07-07-2016
Some shells (such as bash and 1993 or later versions of ksh) provide:
Code:
for((n=1; n<=100; n++))
do	echo "process n=$n"
done

but this is an extension that is not yet specified by the standards. As you said, standard ways to do the same thing require an initialization step before the loop, such as in:
Code:
n=1
while [ $n -le 100 ]
do	echo "process n=$n"
	n=$((n + 1))
done

and in:
Code:
n=0
while [ $((++n <= 100)) -eq 1 ]
do	echo "process n=$n"
done

Note: As noted by Scrutinizer in post #8, the POSIX standards do not require $((++n)) to work. (It works with a recent bash and with a 1993 or later version of ksh, but is an extension to the requirements specified by the standards.)
Code:
n=0
while [ $(((n += 1) <= 100)) -eq 1 ]
do	echo "process n=$n"
done

should work in an POSIX-conforming shell.
Last edited by Don Cragun; 07-10-2016 at 04:56 PM.. Reason: Add note.
This User Gave Thanks to Don Cragun For This Post:
wisecracker
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Hello, I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password. This scares me, for a bunch of reasons. Mainly, one is that we... (1 Reply)
Discussion started by: rwallaceisg
1 Replies

2. UNIX for Dummies Questions & Answers

man synopsis standard compliance

In different online sources, I found bits and pieces of information about those square and angular brackets and pipes. From what I have read, I can conclude it looks like this: 1. Options outside any brackets are mandatory 2. Options inside these < .. > are mandatory too 3. Options inside ... (4 Replies)
Discussion started by: vkleban
4 Replies

3. Cybersecurity

PCI DSS Compliance : Insecure Communication Has Been Detected

From the nessus scanner tool report i got below vulnerability PCI DSS Compliance : Insecure Communication Has Been Detected http://www.tenable.com/plugins/index.php?view=single&id=56208 As per the description given in above link - I am not able to understand How to find insecure port... (2 Replies)
Discussion started by: saurabh84g
2 Replies

4. Red Hat

Looking for PCI Compliance tool for Redhat Lix.

Hi i am in new to Linux world . I have been assigned to a project to find out a tool that will fulfill the PCI compliance for Linux servers for Audit process. anyone have any recommendation on that. Do Rad hat have any native application or plug-ins which we can use for that. (1 Reply)
Discussion started by: sahasuman
1 Replies

5. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:... (0 Replies)
Discussion started by: anaigini45
0 Replies

LEARN ABOUT DEBIAN

surfraw-update-path

SURFRAW-UPDATE-PATH(1)					User Contributed Perl Documentation				    SURFRAW-UPDATE-PATH(1)

NAME

       surfraw-update-path - updates PATH in shell config files

SYNOPSIS

       surfraw-update-path [-add] [-remove] [-check] [-sys] [-all] [-help] [-shell=SHELL]

DESCRIPTION

       surfraw-update-path adds the surfraw elvi directory (/usr/lib/surfraw) to your PATH in your shell's config file.

       Currently it supports bash, sh, csh, tcsh, ash, dash, ksh, pdksh, zsh, rc, and es

       Don't forget to login again or source your login files for it to take effect.

OPTIONS

       -check
	   Checks to see if the surfraw config code is present.  This is the default.

       -add
	   Adds the surfraw config code.

       -remove
	   Removes the surfraw config code

       -sys
	   Updates the system-wide shell config instead of the user.  Must be done as root.

       -shell=SHELL
	   Selects the shell to configure. Defaults to the value of the $SHELL environment variable.

	   Currently supported shells are:

	   sh, ash, bash, dash, csh, tcsh, ksh, pdksh, zsh, rc, and es.

       -all
	   Attempts to configure the startup files for all known shells

       -help
	   Gives a usage message

RETURN VALUE

       -check returns 0 if the surfraw code is present in the file, 1 if it is not found, or 2 on error.

       All other options return 0 on success, or 2 on error.

ENVIRONMENT

       SHELL
	   Used to determine which shell to configure, if -shell is not given.

       HOME
	   Used to find users config files.

       ENV Used by posix-compliant shells to specify a startup rc file.

       ZDOTDIR
	   Used to find user config files for zsh. If not set, defaults to HOME.

SEE ALSO

       surfraw(1), sh(1), ash(1), bash(1), dash(1), csh(1), tcsh(1), ksh(1), pdksh(1), zsh(1), rc(1), es(1)

AUTHOR

       Ian Beckwith <ianb@erislabs.net>

perl v5.12.4							    2011-07-12						    SURFRAW-UPDATE-PATH(1)
All times are GMT -4. The time now is 05:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy