Test command Post: 302399032

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. AIX

Test command

Hello, I am trying to add some tests to existing code. The code already contains some test commands. An example is as follows... ] then Does anyone know the purpose of the double equals? I would have used a single equals sign...

3. 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. Shell Programming and Scripting

Help with test command

Plese help me on the below query. for j in *.20071231* *.ctl *.dat do ( if then cp "$base/*.*" "$base1" fi ) done My requirement is for all files that has extension *.20071231* *.ctl *.dat should be copied to another folder. But those with caaa.20071231.log...

5. Programming

Test command name

I'm very new to C and could use a little help. I'm testing to make sure the command is running as it's proper name, if not then fail. if (strcmp(argv, "xinit") != 0) { fprintf(stdout, "name = %s length = %d\n",argv,l); usage(0); } This works if the command is...

6. UNIX for Dummies Questions & Answers

Test command question

Hi all! I'm new to shell scripting, and I need to do a diff between two dirs. One of them (dir_old) contains many files, and the other (dir_new) contains just a set of 8 files, all starting with MC and extension .CP. The problem I have is that dir_old contains about 20 files that start with...

7. 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...

8. 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

9. Shell Programming and Scripting

TEST Command

Hello, I need help with a test command. Here is what I am trying to do : I've got an interactive script that check if configuration files exist on 2 different directories, then all configuration files are print on screen by a short name. My problem is when you type a "wrong name" or...

10. Shell Programming and Scripting

Evaluation of test command

Could somebody please explain to me why and how the highlighted line(s) (?) of code puts the "test" evaluation into "result" and then to $enable_static ? Or does not ? I did comment out the original code and changed it to what I feel is less cryptic , but the "result" is still wrong =...

LEARN ABOUT MOJAVE

kill.d

kill.d(1m)							   USER COMMANDS							kill.d(1m)

NAME

       kill.d - snoop process signals as they occur. Uses DTrace.

SYNOPSIS

       kill.d

DESCRIPTION

       kill.d is a simple DTrace program to print details of process signals as they are sent, such as the PID source and destination, signal num-
       ber and result.

       This program can be used to determine which process is sending signals to which other process.

       Since this uses DTrace, only users with root privileges can run this command.

EXAMPLES

       Default output, print process signals as they are sent.
	      # kill.d

FIELDS

       FROM   source PID

       COMMAND
	      source command name

       TO     destination PID

       SIG    destination signal ("9" for a kill -9)

       RESULT result of signal (-1 is for failure)

DOCUMENTATION

       See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
       bose descriptions explaining the output.

EXIT

       kill.d will run forever until Ctrl-C is hit.

AUTHOR

       Brendan Gregg [Sydney, Australia]

SEE ALSO

       dtrace(1M), truss(1)

version 0.90							   May 14, 2005 							kill.d(1m)

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

the TEST command

Discussion started by: marwan

2. AIX

Test command

Discussion started by: JWilliams

3. Shell Programming and Scripting

TEST command

Discussion started by: amatuer_lee_3

4. Shell Programming and Scripting

Help with test command

Discussion started by: sussane