Test - too many arguments Post: 302508419

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Can not test many arguments

I'm writing a shell script with bash ver 2.05b in linux. My script has a test with 5 arguments like this: until do .....(some codes) done but it raise an error: [: too many arguments I tried some ways but not ok. Could you give a way to work around this. Thanks...

2. Shell Programming and Scripting

can't TEST multiple arguments for a file

Hi, I'm new to scripting and teaching myself how to code. Using Korn, I coded this one return "True" if a file is executable and it's not empty. However, each time I pass a file that is 777 which contains data, the script returns "false". if then echo "true" else echo...

3. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the...

4. Shell Programming and Scripting

How to check weather a string is like test* or test* ot test in if condition

How to check weather a string is like test* or test* ot *test* in if condition

5. Shell Programming and Scripting

grep with two arguments to arguments to surch for

Hello, is it possible to give grep two documents to surche for? like grep "test" /home/one.txt AND /home/two.txt ? thanks

6. Shell Programming and Scripting

Prefixing test case methods with letter 'test'

Hi, I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the...

LEARN ABOUT FREEBSD

nice

NICE(1) 						    BSD General Commands Manual 						   NICE(1)

NAME

     nice -- execute a utility at an altered scheduling priority

SYNOPSIS

     nice [-n increment] utility [argument ...]

DESCRIPTION

     The nice utility runs utility at an altered scheduling priority, by incrementing its ``nice'' value by the specified increment, or a default
     value of 10.  The lower the nice value of a process, the higher its scheduling priority.

     The superuser may specify a negative increment in order to run a utility with a higher scheduling priority.

     Some shells may provide a builtin nice command which is similar or identical to this utility.  Consult the builtin(1) manual page.

ENVIRONMENT

     The PATH environment variable is used to locate the requested utility if the name contains no '/' characters.

EXIT STATUS

     If utility is invoked, the exit status of nice is the exit status of utility.

     An exit status of 126 indicates utility was found, but could not be executed.  An exit status of 127 indicates utility could not be found.

EXAMPLES

     Execute utility 'date' at priority 5 assuming the priority of the shell is 0:

	   nice -n 5 date

     Execute utility 'date' at priority -19 assuming the priority of the shell is 0 and you are the super-user:

	   nice -n 16 nice -n -35 date

COMPATIBILITY

     The traditional -increment option has been deprecated but is still supported.

SEE ALSO

     builtin(1), csh(1), idprio(1), rtprio(1), getpriority(2), setpriority(2), renice(8)

STANDARDS

     The nice utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').

HISTORY

     A nice utility appeared in Version 4 AT&T UNIX.

BSD
								 February 24, 2011							       BSD