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 CENTOS

nice

NICE(2) 						     Linux Programmer's Manual							   NICE(2)

NAME

       nice - change process priority

SYNOPSIS

       #include <unistd.h>

       int nice(int inc);

   Feature Test Macro Requirements for glibc (see feature_test_macros(7)):

       nice(): _BSD_SOURCE || _SVID_SOURCE || _XOPEN_SOURCE

DESCRIPTION

       nice()  adds  inc to the nice value for the calling process.  (A higher nice value means a low priority.)  Only the superuser may specify a
       negative increment, or priority increase.  The range for nice values is described in getpriority(2).

RETURN VALUE

       On success, the new nice value is returned (but see NOTES below).  On error, -1 is returned, and errno is set appropriately.

ERRORS

       EPERM  The calling process attempted to increase its priority by supplying a negative inc but has insufficient privileges.  Under Linux the
	      CAP_SYS_NICE capability is required.  (But see the discussion of the RLIMIT_NICE resource limit in setrlimit(2).)

CONFORMING TO

       SVr4,  4.3BSD, POSIX.1-2001.  However, the Linux and (g)libc (earlier than glibc 2.2.4) return value is nonstandard, see below.	SVr4 docu-
       ments an additional EINVAL error code.

NOTES

       SUSv2 and POSIX.1-2001 specify that nice() should return the new nice value.  However, the Linux syscall and the  nice()  library  function
       provided  in  older  versions  of  (g)libc (earlier than glibc 2.2.4) return 0 on success.  The new nice value can be found using getprior-
       ity(2).

       Since glibc 2.2.4, nice() is implemented as a library function that calls getpriority(2) to obtain the new nice value to be returned to the
       caller.	 With  this  implementation, a successful call can legitimately return -1.  To reliably detect an error, set errno to 0 before the
       call, and check its value when nice() returns -1.

SEE ALSO

       nice(1), renice(1), fork(2), getpriority(2), setpriority(2), capabilities(7)

COLOPHON

       This page is part of release 3.53 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

Linux								    2007-07-26								   NICE(2)