Hi ,
I am having one situation in which I need to run some simple unix commands after doing "chroot" command in a shell script. Which in turn creates a new shell.
So scenario is that
- I need to have one shell script which is ran as a part of crontab
- in this shell script I need to do a... (2 Replies)
Hi,
First i would like to say that im a unix begginer.
I have a file named /tmp/sample.lst that contain about 20 rows like the following two :
'/tmp/aa.txt' '/temp/aa.txt'
'/tmp/xx.txt' '/temp/xx.txt'
Inside a ksh script i would like to do the following task:
add the cp command at... (2 Replies)
hi,
i wat to get the output of a grep command in a file. but when i am trying out the same grep command in the unix prompt its working fine.. i am getting the output properly.. but when i am writing the same command inside my shell script , its just creating a new output file with no contents... (1 Reply)
hi,
i wat to get the output of a grep command in a file. but when i am trying out the same grep command in the unix prompt its working fine.. i am getting the output properly.. but when i am writing the same command inside my shell script , its just creating a new output file with no contents... (11 Replies)
I have a command nested in some while loops to parse some data that looks something like this.
while ($condition)
while ($condition)
...
gzcat /dir/$fileName.gz | grep $searchString > out_file
end
end
On the first loop, the command is executed properly (and takes maybe 10... (3 Replies)
Hi all,
I am using the below given sqlplus command in my unix script to invoke a stored procedure which returns a value .It works fine.
RET_CODE=$(/opt/oracle/product/10.2.0.4.CL/bin/sqlplus -S $USER/$PASSWD@$DB_NAME <<EOF
EXEC MY_PKG.MY_SP (:COUNT);
PRINT COUNT;
commit;
... (6 Replies)
Hi everyone,
when executing this command in unix:
echo "WM7 Fatal Alerts:", $(cat query1.txt) > a.csvIt works fine, but running this command in a shell script gives an error saying that there's a syntax error.
here is content of my script:
tdbsrvr$ vi hc.sh
"hc.sh" 22 lines, 509... (4 Replies)
Hello,
Recently, I've started with shell scripting, and decided to write a script for my system backup using tar. When I was dealing with tar execution inside shell script I found this, inside shell we have the following code:
tar $TAR_PARAMS $ARCHIVE_FILE $EXCLUDE $BACKUP_STARTwith... (6 Replies)
hii,,
I am trying to automate jira. during my scripting using bash script, in the terminal i got the terminal message like this:
"Configure which ports JIRA will use.
JIRA requires two TCP ports that are not being used by any other
applications on this machine. The HTTP port is where you... (1 Reply)
#!/bin/sh
# This script returns the number of rows updated from a function
echo "The execution is starting ....."
sqlplus -silent $UP <<EOF
set serveroutput on
set echo off
set pagesize 0
VAR no_rows_updated NUMBER;
EXEC :no_rows_updated :=0;
DECLARE
CURSOR c_update is
SELECT * FROM... (4 Replies)
Discussion started by: LoneRanger
4 Replies
LEARN ABOUT OPENSOLARIS
return
exit(1) User Commands exit(1)NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps
SYNOPSIS
sh
exit [n]
return [n]
csh
exit [( expr )]
goto label
ksh
*exit [n]
*return [n]
ksh93
+exit [n]
+return [n]
DESCRIPTION
sh
exit causes the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of the
last command executed (an EOF also causes the shell to exit.)
return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe-
cuted.
csh
exit causes the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the
expression expr.
The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches
for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to
jump to a label that occurs between a while or for built-in command and its corresponding end.
ksh
exit causes the calling shell or shell script to exit with the exit status specified by n. The value is the least significant 8 bits of the
specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing a trap, the
last command refers to the command that executed before the trap was invoked. An end-of-file also causes the shell to exit except for a
shell which has the ignoreeof option (See set below) turned on.
return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value is the least
significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return is
invoked while not in a function or a '.' script, then it is the same as an exit.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a
variable assignment. This means that tilde substitution is performed after the = sign and word splitting and file name genera-
tion are not performed.
ksh93
exit is shell special built-in that causes the shell that invokes it to exit. Before exiting the shell, if the EXIT trap is set, it is
invoked.
If n is specified, it is used to set the exit status.
return is a shell special built-in that causes the function or dot script that invokes it to exit. If return is invoked outside of a func-
tion or dot script it is equivalent to exit.
If return is invoked inside a function defined with the function reserved word syntax, then any EXIT trap set within the function is
invoked in the context of the caller before the function returns.
If n is specified, it is used to set the exit status.
On this manual page, ksh93 commands that are preceded by one or two + symbols are special built-in commands and are treated specially in
the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. They are not valid function names.
5. Words following a command preceded by ++ that are in the format of a variable assignment are expanded with the same rules as a
variable assignment. This means that tilde substitution is performed after the = sign and field splitting and file name genera-
tion are not performed.
EXIT STATUS
ksh93
If n is specified for exit, the exit status is the least significant eight bits of the value of n. Otherwise, the exit status is the exit
status of preceding command. When invoked inside a trap, the preceding command means the command that invoked the trap.
If n is specified for return, the exit status is the least significant eight bits of the value of n. Otherwise, the exit status is the exit
status of preceding command.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO break(1), csh(1), ksh(1), ksh93(1), sh(1), attributes(5)SunOS 5.11 2 Nov 2007 exit(1)