I know that the exit codes in scripting "$*" will returns all the parameters/arguments passwd to the script.
But I also know that "$@" will also returns the same. What is the difference between those two [ $* and $@ ] ?
"$*" and "$@" are not exit codes; they are the command line arguments.
Exit codes are stored in "$?".
When unquoted, $* and $@ are the same; each word in the argument list becomes a separate word.
When quoted, "$*" returns a single argument containing all the command-line arguments; "$@" presents each command-line argument as a separate argument.
For a demonstration, put the following into a script and exceute it with the arguments: a "b c" "d e f" g.
This User Gave Thanks to cfajohnson For This Post:
I'm receiving an exit code 64 in our batch scheduler (BMC product control-m) executing a PERL script on UX-HP. Can you tell me where I can find a list of exit codes and their meaning. I'm assuming the exit code is from the Unix operating system not PERL. (3 Replies)
I have a Unix Script that has several exit in the middle. each returning seperate
exit codes.
I have to catch all the exit's and perform an operation say "Mail the status code" before the actual code completes.
How can i do this in KSH ? (3 Replies)
HI All,
I have created a unix script which takes 2 parameters and using sftp tranfers files to remote location
following is the script
#!/bin/ksh
#
#
# Parameter 1 is the complete path of the destination server
# Parameter 2 is the complete path of the file which is to be FTP... (1 Reply)
Good Morning All..
I was wondering about getting exit codes of a command in a shell script. I'm trying to run uvscan (McAfee command line scanner) and I want to have the log file say why, if at all, the process failed/exited.
Something to the extent of
If ; then
echo "This is why it... (1 Reply)
Hello,
I need to ensure that SCP does not leave any partially transmitted files on the remote server due to transmission errors.
Can it be assumed that:
1) if SCP returns a success with Exit Code == 0, a complete local file has been copied in its entirety to the remote location?
2)... (1 Reply)
how do i/is there a way to return the exit code from the remote host?
echo $? from the local host only gives 0, if the rexec command itself executes successfully. But what if in the case of the remote command failiing? echo $? on the localhost still gives 0, but I'm interested in the exit code... (4 Replies)
I am trying to run this SH on Linux and getting error at IF condition.
I want to read the EXIT code and send the failure or success message.
Please help me on this. This worked when i was running on Solaris.
#!/bin/bash
$ORACLE_HOME/bin/sqlplus abc/xyz@qwe @/home/test.sql
if ;... (4 Replies)
I have a script which connects to a remote server via FTP and gets some file from there.
#!/bin/bash
/usr/bin/ftp -n remote.hostname.com <<EOF
quote USER user123
quote PASS password123
lcd /dir1/dir2/dir3
cd /
mget file_pattern*
close
bye
EOF
rc=$?
if ]
... (7 Replies)
Discussion started by: dhruuv369
7 Replies
LEARN ABOUT OSX
xprintf_comp
XPRINTF_COMP(3) BSD Library Functions Manual XPRINTF_COMP(3)NAME
free_printf_comp, new_printf_comp -- extensible printf compilation
SYNOPSIS
#include <printf.h>
void
free_printf_comp(printf_comp_t pc);
printf_comp_t
new_printf_comp(printf_domain_t restrict domain, locale_t restrict loc, const char * restrict fmt);
DESCRIPTION
To ameliorate some of the slowness caused by the extra overhead in extensible printf (see xprintf(5)), a compile/execute mechanism has been
created. The new_printf_comp() function compiles the given format string, along with a printf domain (see xprintf_domain(3)) and an extended
locale (see xlocale(3)), and returns a printf_comp_t structure. The domain may not be NULL, but the locale can be NULL, which means to use
the current locale, either the per-thread locale if it was set, or else the global locale. Because the printf_comp_t structure records the
domain and locale, care should be taken if either of these are changed.
Once a printf_comp_t structure is created, it can be passed to one of the extensible printf execution variants, described in xprintf_exec(3),
along with the necessary arguments. Creating the printf_comp_t structure needs to be done only once, but it can be passed to extensible
printf execution variants any number of times.
When the printf_comp_t structure is no longer needed, it should be passed to free_printf_comp() to release internal memory.
RETURN VALUES
The new_printf_comp() function returns the new structure, or NULL on error (usually NULL domain or out of memory condition).
SEE ALSO xlocale(3), xprintf_domain(3), xprintf_exec(3), xprintf(5)Darwin Aug 19, 2012 Darwin