Sponsored Content
Full Discussion: test command is not working
Top Forums Shell Programming and Scripting test command is not working Post 302078697 by zam on Tuesday 4th of July 2006 04:32:30 AM
Old 07-04-2006
test command is not working

#!/bin/ksh
size=3978132853
limit=100
if [ $size -gt $limit ];then
echo exceeded limit
fi

This does not work though if i reduce 3978132853 to 397813285 it works any ideas and work around appreciated

(SunOS 5.9 Generic_117171-02 sun4u sparc SUNW,Ultra-80 )
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

the TEST command

Hi everyone, I am new to UNIX and scripting, and I have some problems with the test command. when i try to execute the command: test 20070327.gz > 20070320.gz i try to make a charachter string comparison between the two strings or the two files, to make sure that 20070327.gz is greater than... (2 Replies)
Discussion started by: marwan
2 Replies

2. Shell Programming and Scripting

TEST command

I have been looking into searching various files to display output. The search criteria will be a month and year to output various numbers in the files. is there any way to do this with the TEST function or would it have to be another way? (4 Replies)
Discussion started by: amatuer_lee_3
4 Replies

3. Solaris

How i test the UDP port is working?

Hi anybody know how to test out the UDP port working? cos UDP cannot use telnet to test... Sumemr (2 Replies)
Discussion started by: summerpeh
2 Replies

4. 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... (1 Reply)
Discussion started by: Max89
1 Replies

5. 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 Replies)
Discussion started by: johnjerome
5 Replies

6. UNIX for Advanced & Expert Users

if and test not working

All, I am getting error when run file check with test operator . Why is it showing the error if then echo 'file found' fi ksh: -r: unknown test operator I know i can use the below code to test the file but why the above is not working if test -r filename ... (3 Replies)
Discussion started by: arunkumar_mca
3 Replies

7. Shell Programming and Scripting

String == isn't working in [[-test

Hi. I'm new to this forum, my English perhaps is not so good, but here is my question: In bash you can use ] for tests, and how I understand it the variable names should be expanded automatically. So this should give "yes": xx=hello $ ] && echo yes || echo no no # not giving "yes" These two... (2 Replies)
Discussion started by: 244an
2 Replies

8. Shell Programming and Scripting

Use The Terminal To Test Arduino Is Working.

Hi all... (Apologies for any typos at all.) This is a step by step _script_ to check if your Arduino is talking to your Linux or Macbook Pro computer using the Terminal... It works on at least 3 Linux flavours and now the Macbook Pro... I hope you find it useful as a simple check for... (0 Replies)
Discussion started by: wisecracker
0 Replies

9. Shell Programming and Scripting

Test function not working

i am writing the following snippet and cannot figure out why the variable measType remains 0. it should be 1 I also tried "\#analog" and '\#analog' in the test statement and it still doesn't work. What is going on? bash$ measType=0 bash$ read line < 2iconfig.ini bash$ echo $line #analog... (4 Replies)
Discussion started by: oahmad
4 Replies

10. UNIX for Advanced & Expert Users

Test -e not working as expected (by me)

I ran into the following and still do not understand entirely the rationale behind this. If someone could explain why things are as they are I'd be thankful. The following was tested on AIX 7.1 with ksh88, but i suspect that to be ubiquitous. In an installation routine i had to create a set of... (6 Replies)
Discussion started by: bakunin
6 Replies
vlimit(3)						     Library Functions Manual							 vlimit(3)

Name
       vlimit - control maximum system resource consumption

Syntax
       #include <sys/vlimit.h>

       vlimit(resource, value)

Description
       This facility has been superseded by

       Limits  the  consumption by the current process and each process it creates to not individually exceed value on the specified resource.	If
       value is specified as -1, then the current limit is returned and the limit is unchanged.  The resources which  are  currently  controllable
       are:

       LIM_NORAISE    Pseudo-limit; if set nonzero then the limits may not be raised.  Only the super-user may remove the noraise restriction.

       LIM_CPU	      The maximum number of cpu-seconds to be used by each process.

       LIM_FSIZE      The largest single file which can be created.

       LIM_DATA       The maximum growth of the data+stack region via beyond the end of the program text.

       LIM_STACK      The maximum size of the automatically-extended stack region.

       LIM_CORE       the size of the largest core dump that will be created.

       LIM_MAXRSS     a  soft  limit for the amount of physical memory (in bytes) to be given to the program.  If memory is tight, the system will
		      prefer to take memory from processes which are exceeding their declared LIM_MAXRSS.

       Because this information is stored in the per-process information this system call must be executed directly by	the  shell  if	it  is	to
       affect all future processes created by the shell; limit is thus a built-in command to

       The  system  refuses to extend the data or stack space when the limits would be exceeded in the normal way.  A break call fails if the data
       space limit is reached, or the process is killed when the stack limit is reached.  Since the stack cannot be extended, there is no  way	to
       send a signal.

       A file I/O operation which would create a file which is too large will cause a signal SIGXFSZ to be generated, this normally terminates the
       process, but may be caught.  When the cpu time limit is exceeded, a signal SIGXCPU is sent to the offending process; to allow  it  time	to
       process the signal it is given 5 seconds grace by raising the cpu time limit.

Restrictions
       If LIM_NORAISE is set, then no grace should be given when the CPU time limit is exceeded.

See Also
       csh(1)

																	 vlimit(3)
All times are GMT -4. The time now is 10:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy