Hi,
I want to find the exit status of the last executed command in C Shell.
Tried $? but getting the error Variable syntax...$? does not seem to work in C shell..
is there any other command in C shell to find the exit status of last command?
Thanks in advance,
raju (1 Reply)
Hi,
I have tried with the following code;
if ;then
echo "Failure."
else
echo "Success."
fi
to test the exit status of the test.ksh shell script. But whatever is the exit status of the test.ksh shell script Failure. is always printed.
Please help.
regards,
Dipankar. (2 Replies)
Hi All,
I have developed below script for FTP a file from unix machine to another machine.
ftpToABC ()
{
USER='xyz'
PASSWD='abc'
echo "open xx.yy.zbx.aaa
user $USER $PASSWD
binary
echo "put $1 abc.txt" >> /home/tmp/ftp.$$
echo "quit" >> /home/tmp/ftp.$$
ftp -ivn <... (3 Replies)
Hi,
I have a below command....
$JAVA_HOME/bin/java -cp "/usr/orabase/product/10.2.0/lib:/usr/java/javajar/common/sched.jar:/usr/orabase/product/10.2.0/jdbc/lib/ojdbc14_g.jar:/usr/orabase/product/10.2.0/jdbc/lib/classes12.jar" com.abrt.smart.Smart
I want to know where the Smart.class is... (1 Reply)
Hi All,
I have a scenario where I am executing some child shell scripts in background (using &)through a master parent script.
Is there a way I can capture the exit status of each individual child script after the execution is completed. (2 Replies)
Hello All
My req is to store the exit status of a command in shell variable
I want to check whether the file has header or not
The header will contain the string
DATA_ACQ_CYC_CNTL_ID
So I am running the command
head -1 $i | grep DATA_ACQ_CYC_CNTL_ID
Now I have to check if... (6 Replies)
I have a script named check which will read the content of a file and check wether those files exist in the current directory. If so it will have the exit status of 0, otherwise it will have 1.
check script:
#!/bin/bash
if ; then #Check there is enough command line parameters.
exit 1... (2 Replies)
Hi there,
I'm very used to use set -e to break my scripts if any command exits with a non-zero status.
As a policy, I'm willingly expecting echo hello | grep a to break the script.
The commands test 1 -eq $1 && echo hello exits with a non-zero status if $1 is not 1. BUT... It doesn't break... (2 Replies)
Have no idea on what the below error message is:
Process not running: /opt/java15/jdk/bin/java -classpath /opt/apache/apache-ant-1.7.0-mod/lib/ant-launcher.jar org.apache.tools.ant.launch.Launcher -buildfile build.xml dist.
Any help? (3 Replies)
Discussion started by: gull05
3 Replies
LEARN ABOUT DEBIAN
mh_installjar
MAVEN(1) User Commands MAVEN(1)NAME
Maven - Installs a jar into /usr/share/maven-repo.
SYNOPSIS
mh_installjar [option]... [pom] [jar] [link]...
DESCRIPTION
Installs the jar file in /usr/share/maven-repo, at the correct location for Maven. The jar is copied into the build directory. It can also
create additional links to the jar, usually located in /usr/share/java.
Where
[pom] is the location of the POM associated with the jar to install.
GroupId, artifactId and version will be extracted from this file.
[jar] is the path to the jar to install, usually located in the build
folder.
[link] is an additional link to the jar to install, usually there should
be a link to usr/share/java/$jar.jar and usr/share/java/$jar-$version.jar to comply with the Java packaging guidelines. Note that
there is no need to specify those particular links if the --java-lib option is used.
OPTIONS -h --help: show this text
-V --version: show the version
-p<package> --package=<package>: name of the Debian package which
will contain this jar file
-e<version>, --set-version=<version>: set the version for the jar,
do not use the version declared in the POM file.
-r<rules> --rules=<rules>: path to the file containing the
rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules Maven rules are used here to extract the
groupId, artifactId and version from the POM file.
-l --java-lib: Optional, if given it will install the jar into
/usr/share/java to comply with the Debian Java specification. The jar will be installed as /usr/share/java/$name-$version.jar and a
versionless link /usr/share/java/$name.jar will point to it, as well as the links installed in /usr/share/maven-repo
-n<name> --usj-name=<name>: Optional, the name to use when installing the
library in /usr/share/java when --java-lib is used. Defaults to the artifact id found in the POM.
-j<version> --usj-version=<version>: Optional, the version to use when
installing the library in /usr/share/java when --java-lib is used. Defaults to the version found in the POM.
-s --no-usj-versionless: Optional, don't install the versionless link
in /usr/share/java. This flag is used only when the -l or --java-lib option is given.
-d<path> --dest-jar=<path>: Optional, the destination for the real jar.
The other places where the jar appears, in the repository or in the list of links, will be symlinks to this jar. Defaults to
/usr/share/java/$name-$version.jar if --java-lib is used, otherwise the jar is installed in the versioned path in the Maven reposi-
tory.
-c<classifier> --classifier=<classifier>: Optional, the classifier for
the jar. Empty by default.
-v --verbose: show more information while running
-n --no-act: don't actually do anything, just print the results
--skip-clean-pom: don't clean the pom, assume that a previous action ran
mh_cleanpom with the correct options. mh_cleanpom is run only to extract the groupId, artifactId and version of the jar
See also: mh_installpom(1), mh_installsite(1)Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)