i downloaded a text file from metalab.unc.edu called sh.txt and in this reference manual it refers to shell scripting exit status .. at the end of one of the examples that author gave an exit status of 127..
to what does a 127 exit status refer too and what is its purpose in the code.
moxxx68 (1 Reply)
I'm trying to write a script that will update a table in sysbase.
If it's failed then I want to rerun it one more time before exiting the script (fail due to bad value such as trying to put a string into datetime field or bad connection to the database)
Well my code below will always return... (2 Replies)
Hi all,
I'm running a program which return 1 upon success.
But when encounters problem shell return 's '1' .
How to differentiate between them the shell return value and script return value.
Ex. function fn return '1' if executed successfully and '0' if failed. But when if shell encounters... (1 Reply)
I'm preparing for exam and one of exams is to write own test command...
I wonder if in unix is a command which just returns exit code you specify..
I know I can easily write a function like this:
exStatus() {
return $1
}
-> my question is rather theoretical
thank you! (9 Replies)
I am trying to get the exit status of grep and test a condition with it, But it does not seem to be working as expected since i am doing something wrong apparently
as per grep help
Exit status is 0 if match, 1 if no match,
and 2 if trouble.
My problem is something like this
templine - a... (7 Replies)
Hi,
I'm having this simple code below, the file serverlist has a list of IPs one per line. When executed the while loop is executed only once, after that the program terminates. How should i redirect the exit status, so that the entire list of IP will get executed?
#!/bin/bash
exec <... (4 Replies)
Lois_Answer_Code=`sipsak -vv -s sip:192.168.1.3|grep -A 1 "reply received after"|grep SIP|awk '{print $2}'`How to find the exit status of | (12 Replies)
I have a shell script (#!/bin/sh) that interacts with Appworx and Banner Admin. In my script I want to check the exit status of awrun before continuing. awrun can run for 10 seconds or it can run for over a minute. So my question is, will it go through my if statement before awrun may even be... (2 Replies)
Hi All,
I have a peculiar requirement as follows,
I have a some hosts on which i have to run a script, so i am using the following code piece
for i in $HOSTLIST
do
ssh ${i} "~/task.sh"
done
Now i want to run this same thing in parallel on all the hosts and then monitor the ssh process... (1 Reply)
Hi All,
I am trying to create a zip file with all the txt files(these are in large number) in the current directory. I am able to do this operation sucessfully.
After this i want to get the status of the tar command executed and do accordingly. When i am trying with the below code, the status... (3 Replies)
Discussion started by: paddu
3 Replies
LEARN ABOUT SUNOS
runat
runat(1) User Commands runat(1)NAME
runat - execute command in extended attribute name space
SYNOPSIS
/usr/bin/runat file [command]
DESCRIPTION
The runat utility is used to execute shell commands in a file's hidden attribute directory. Effectively, this utility changes the current
working directory to be the hidden attribute directory associated with the file argument and then executes the specified command in the
bourne shell (/bin/sh). If no command argument is provided, an interactive shell is spawned. The environment variable $SHELL defines the
shell to be spawned. If this variable is undefined, the default shell, /bin/sh, is used.
The file argument can be any file, including a directory, that can support extended attributes. It is not necessary that this file have any
attributes, or be prepared in any way, before invoking the runat command.
OPERANDS
The following operands are supported:
file Any file, including a directory, that can support extended attributes.
command The command to be executed in an attribute directory.
ERRORS
A non-zero exit status will be returned if runat cannot access the file argument, or the file argument does not support extended
attributes.
USAGE
See fsattr(5) for a detailed description of extended file attributes.
The process context created by the runat command has its current working directory set to the hidden directory containing the file's
extended attributes. The parent of this directory (the ".." entry) always refers to the file provided on the command line. As such, it may
not be a directory. Therefore, commands (such as pwd) that depend upon the parent entry being well-formed (that is, referring to a direc-
tory) may fail.
In the absence of the command argument, runat will spawn a new interactive shell with its current working directory set to be the provided
file's hidden attribute directory. Notice that some shells (such as zsh and tcsh) are not well behaved when the directory parent is not a
directory, as described above. These shells should not be used with runat.
EXAMPLES
Example 1: Using runat to list extended attributes on a file
example% runat file.1 ls -l
example% runat file.1 ls
Example 2: Creating extended attributes
example% runat file.2 cp /tmp/attrdata attr.1
example% runat file.2 cat /tmp/attrdata > attr.1
Example 3: Copying an attribute from one file to another
example% runat file.2 cat attr.1 | runat file.1 "cat > attr.1"
Example 4: Using runat to spawn an interactive shell
example% runat file.3 /bin/sh
This spawns a new shell in the attribute directory for file.3. Notice that the shell will not be able to determine what your current direc-
tory is. To leave the attribute directory, either exit the spawned shell or change directory (cd) using an absolute path.
Recommended methods for performing basic attribute operations:
display
runat file ls [options]
read
runat file cat attribute
create/modify
runat file cp absolute-file-path attribute
delete
runat file rm attribute
permission changes
runat file chmod mode attribute
runat file chgrp group attribute
runat file chown owner attribute
interactive shell
runat file /bin/sh
or set your $SHELL to /bin/sh and
runat file
The above list includes commands that are known to work with runat. While many other commands may work, there is no guarantee that any
beyond this list will work. Any command that relies on being able to determine its current working directory is likely to fail. Examples of
such commands follow:
Example 5: Using man in an attribute directory
example% runat file.1 man runat
getcwd: Not a directory
Example 6: Spawning a tcsh shell in an attribute directory
example% runat file.3 /usr/bin/tcsh
tcsh: Not a directory
tcsh: Trying to start from "/home/user"
A new tcsh shell has been spawned with the current working directory set to the user's home directory.
Example 7: Spawning a zsh shell in an attribute directory
example% runat file.3 /usr/bin/zsh
example%
While the command appears to have worked, zsh has actually just changed the current working directory to '/'. This can be seen by using
/bin/pwd:
example% /bin/pwd
/
ENVIRONMENT VARIABLES
SHELL Specifies the command shell to be invoked by runat.
EXIT STATUS
The following exit values are returned:
125 The attribute directory of the file referenced by the file argument cannot be accessed.
126 The exec of the provided command argument failed.
Otherwise, the exit status returned is the exit status of the shell invoked to execute the provided command.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|CSI |Enabled |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO open(2), attributes(5), fsattr(5)NOTES
It is not always obvious why a command fails in runat when it is unable to determine the current working directory. The errors resulting
can be confusing and ambiguous (see the tcsh and zsh examples above).
SunOS 5.10 22 Jun 2001 runat(1)
09-11-2011
)