Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Return Status
Top Forums Shell Programming and Scripting Return Status Post 302519124 by mirni on Tuesday 3rd of May 2011 05:17:59 AM
Old 05-03-2011
They are both positional parameters. Variables that store all your arguments. Useful e.g. when you can loop through arguments.
Quote:
$@ is same as $*, but each parameter is a quoted string, that is, the parameters are passed on intact, without
interpretation or expansion. This means, among other things, that each parameter in the argument list
is seen as a separate word.
from Advanced bash scripting guide
Look here for examples:
Special Variable Types
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Return status...

Hello there! Here is my problem. I hope I can get some help about it. I need to know how can I get the return code of an application in the Unix shell script. The script is like below: PREVIOUS STATEMENT & VARIABLES sqlplus scott/tiger @$sqldir/$sqlscript NEXT STATEMENT (Like... (7 Replies)
Discussion started by: Shaz
7 Replies

2. Shell Programming and Scripting

return ftp status

Hello, I still have problems when trying to figure out if the status of an ftp was successful. I ftp to different types (nt, vax, unix, etc...) of machines. I am trying to write a universal script that will ftp a file and then check to see if the ftp was successful. I have tried the... (12 Replies)
Discussion started by: blt123
12 Replies

3. Shell Programming and Scripting

Return status of all previous runs

hi, I set the crontab to execute script A every 5 minutes from 9:00 am to 4:00 pm everyday, now at 12:00am I want to run another script if and only if all the previous runs of script A return OK, can anyone tell me how it could be done? thank you very very much! (4 Replies)
Discussion started by: mpang_
4 Replies

4. Shell Programming and Scripting

Verify scp return status

Hi all below is a snippet of my perl codesystem ("scp -pq $dest_file $path");How i can i trap the return status? ie if the scp fails how can i know ? (2 Replies)
Discussion started by: new2ss
2 Replies

5. HP-UX

Return of EXIT status ( $? )

I have the question: How return the exit code from then assign : VAR=$(command ) for ex. VAR=$(ls ....) VAREXIT=$? echo $VAREXIT VAREXIT is equal to 0 if the directory exist or not exist. WHI?? if i execute the command direct from line-command , the value of $? is different if... (1 Reply)
Discussion started by: ZINGARO
1 Replies

6. Shell Programming and Scripting

evaluate return status of a function

Hi all I'm trying to evalute the return status of a function without much success. I've put a very basic example below to explain. check_ok() works fine but when used within an if statement, it always returns true, whether it is true or false. I'm guessing it returns true as the function... (4 Replies)
Discussion started by: tig2810
4 Replies

7. Shell Programming and Scripting

capturing C++ binary return status in perl

Hello, I have a C++ binary that runs in my perl script. But, Currently, the binary is doing a core dump and i want to capture the retrun status of the binary to report as an issue. Can you please help me on this. Thanks, Sateesh (1 Reply)
Discussion started by: kotasateesh
1 Replies

8. Shell Programming and Scripting

capturing C++ binary return status in perl

Hello, I have a C++ binary that runs in my perl script. But, Currently, the binary is doing a core dump and i want to capture the retrun status of the binary to report as an issue. Can you please help me on this. Thanks, Sateesh (1 Reply)
Discussion started by: kotasateesh
1 Replies

9. Shell Programming and Scripting

checking for return status between multiple commands

i have to run set of commands command1 command2 command3 command4 Now Whenever any of these command fails i should quit while capturing error message. Is there a better way then checking for $? after each command. (1 Reply)
Discussion started by: vickylife
1 Replies

10. UNIX for Dummies Questions & Answers

opposite return status in c shell

there is something wrong with my system. when I do this: diff file1 file1 && echo 1 the output is 1. but diff file1 file2 >/dev/null && echo 1 output nothing while diff file1 file2 >/dev/null || echo 1 shows 1. the same with "grep" return status. they are both GNU utilities.... (5 Replies)
Discussion started by: phil518
5 Replies

LEARN ABOUT REDHAT

http::status

HTTP::Status(3) 					User Contributed Perl Documentation					   HTTP::Status(3)

NAME

       HTTP::Status - HTTP Status code processing

SYNOPSIS

	use HTTP::Status;

	if ($rc != RC_OK) {
	    print status_message($rc), "
";
	}

	if (is_success($rc)) { ... }
	if (is_error($rc)) { ... }
	if (is_redirect($rc)) { ... }

DESCRIPTION

       HTTP::Status is a library of routines for defining and classifying HTTP status codes for libwww-perl.  Status codes are used to encode the
       overall outcome of a HTTP response message.  Codes correspond to those defined in RFC 2616 and RFC 2518.

CONSTANTS

       The following constant functions can be used as mnemonic status code names:

	  RC_CONTINUE			       (100)
	  RC_SWITCHING_PROTOCOLS	       (101)
	  RC_PROCESSING 		       (102)

	  RC_OK 			       (200)
	  RC_CREATED			       (201)
	  RC_ACCEPTED			       (202)
	  RC_NON_AUTHORITATIVE_INFORMATION     (203)
	  RC_NO_CONTENT 		       (204)
	  RC_RESET_CONTENT		       (205)
	  RC_PARTIAL_CONTENT		       (206)
	  RC_MULTI_STATUS		       (207)

	  RC_MULTIPLE_CHOICES		       (300)
	  RC_MOVED_PERMANENTLY		       (301)
	  RC_FOUND			       (302)
	  RC_SEE_OTHER			       (303)
	  RC_NOT_MODIFIED		       (304)
	  RC_USE_PROXY			       (305)
	  RC_TEMPORARY_REDIRECT 	       (307)

	  RC_BAD_REQUEST		       (400)
	  RC_UNAUTHORIZED		       (401)
	  RC_PAYMENT_REQUIRED		       (402)
	  RC_FORBIDDEN			       (403)
	  RC_NOT_FOUND			       (404)
	  RC_METHOD_NOT_ALLOWED 	       (405)
	  RC_NOT_ACCEPTABLE		       (406)
	  RC_PROXY_AUTHENTICATION_REQUIRED     (407)
	  RC_REQUEST_TIMEOUT		       (408)
	  RC_CONFLICT			       (409)
	  RC_GONE			       (410)
	  RC_LENGTH_REQUIRED		       (411)
	  RC_PRECONDITION_FAILED	       (412)
	  RC_REQUEST_ENTITY_TOO_LARGE	       (413)
	  RC_REQUEST_URI_TOO_LARGE	       (414)
	  RC_UNSUPPORTED_MEDIA_TYPE	       (415)
	  RC_REQUEST_RANGE_NOT_SATISFIABLE     (416)
	  RC_EXPECTATION_FAILED 	       (417)
	  RC_UNPROCESSABLE_ENTITY	       (422)
	  RC_LOCKED			       (423)
	  RC_FAILED_DEPENDENCY		       (424)

	  RC_INTERNAL_SERVER_ERROR	       (500)
	  RC_NOT_IMPLEMENTED		       (501)
	  RC_BAD_GATEWAY		       (502)
	  RC_SERVICE_UNAVAILABLE	       (503)
	  RC_GATEWAY_TIMEOUT		       (504)
	  RC_HTTP_VERSION_NOT_SUPPORTED        (505)
	  RC_INSUFFICIENT_STORAGE	       (507)

FUNCTIONS

       The following additional functions are provided.  Most of them are exported by default.

       status_message($code)
	   The status_message() function will translate status codes to human readable strings. The string is the same as found in the constant
	   names above.  If the $code is unknown, then "undef" is returned.

       is_info($code)
	   Return TRUE if $code is an Informational status code.  This class of status code indicates a provisional response which can't have any
	   content.

       is_success($code)
	   Return TRUE if $code is a Successful status code.

       is_redirect($code)
	   Return TRUE if $code is a Redirection status code. This class of status code indicates that further action needs to be taken by the
	   user agent in order to fulfill the request.

       is_error($code)
	   Return TRUE if $code is an Error status code.  The function return TRUE for both client error or a server error status codes.

       is_client_error($code)
	   Return TRUE if $code is an Client Error status code. This class of status code is intended for cases in which the client seems to have
	   erred.

	   This function is not exported by default.

       is_server_error($code)
	   Return TRUE if $code is an Server Error status code. This class of status codes is intended for cases in which the server is aware that
	   it has erred or is incapable of performing the request.

	   This function is not exported by default.

BUGS

       Wished @EXPORT_OK had been used instead of @EXPORT in the beginning.  Now too much is exported by default.

libwww-perl-5.65						    1999-11-22							   HTTP::Status(3)
All times are GMT -4. The time now is 01:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy