Hi folks!
my client uses an winapplication which is launching shell-scripts remotely on a HP-Unix Machine via Rexec.
The application-configuration is launching the script (which is in the home directory of connecting user) like:
rexec host user pass shell.sh
So far so good, everything... (3 Replies)
hi there,
i need some help, i am trying to run a script to launch a C program and a Java program but before running both I want to get a user input and then invoke both programs with input received. In the programs the inputs are not command line arguments.
This is the code,
after the java... (4 Replies)
I'm working on a function in a shell script I'm writing that will eventually take in and print out a list of vendor names and aliases (for my work) Here's the function in question:
addvendorandalias ()
{
echo
echo -n 'Would you like to create a new vendor list (y or n)? '
read answer... (3 Replies)
Hi everybody,
I have compiled my code based on the ALPS libraries () and CMake build system with IBM compiler xlC 11.1 on AIX 6.1 at the latest patch level running on an IBM SP Power 6 machine for high-performance computing.
When I run the executable I receive this error message:
-bash-3.2$... (2 Replies)
Hi,
I have a shell script which is residing on AIX which is triggered by Mainframe through Connect Direct. The shell script creates several files and sends those files to mainframe using Connect Direct. The shell script is working fine, still it is returning exit code 2 to mainframe.
What... (0 Replies)
Hi,
I am writing a script in which I am using an IF-Else statement.
Code sample:
# Check for the product.
If (test "$3" = "Pet") Then
Product_Code="PI"
elif (test "$3" = "Breakdown") Then
Product_Code="RI"
elif (test "$3" = "Travel") Then
Product_Code="TI"
... (2 Replies)
Hi,
I have initailized a varaible EBID as typeset Long EBID=0
i am calculating value of EBID using certian formula as below:
(( CURR_EBID= ($BANDINDEX << 27) | ($CURR_FREQ << 16) | ($CURR_CELLID << 4) | $CURR_SECTOR_VALUE ))
return $CURR_EBID
The output is as below:
+ (( CURR_EBID=... (6 Replies)
Hi all,
i have the following script
#!/bin/sh
for i in `ps -leaf --cols 1024 | grep LogUser | grep -v grep | awk '{print $4}'`;
do
echo $i
kill -15 $i;
done;
but it seems that the crontab its sciping this script,i configured corntab as following
*/30 * * * root... (2 Replies)
The code at the bottom is a simplified example of what we have.
If I use the following:
&& echo "echo failed"
$? returns 1
When I use
if ; then echo "echo failed" ; fi
$? returns 0
Does anyone know what's wrong with this?
Using AIX 6.1 and KSH
for NUM in 1 2 3
do
... (5 Replies)
I'm using the Links2 console web browser in graphical mode (the "-g" argument), and launching a shell script
that invokes MPlayer from within it. MPlayer works fine. No problem there. The problem, is that I have no
control over the MPlayer process. I would like to be able to exit MPlayer whenever... (16 Replies)
Discussion started by: ignatius
16 Replies
LEARN ABOUT SUSE
lsb_release
FSG(1) FSG FSG(1)NAME
FSG - manual page for FSG lsb_release v2.0-SuSE
SYNOPSIS
lsb_release [OPTION]...
DESCRIPTION
FSG lsb_release v2.0-SuSE prints certain LSB (Linux Standard Base) and Distribution information.
With no OPTION specified defaults to -v.
OPTIONS -v, --version
Display the version of the LSB specification against which the distribution is compliant.
-i, --id
Display the string id of the distributor.
-d, --description
Display the single line text description of the distribution.
-r, --release
Display the release number of the distribution.
-c, --codename
Display the codename according to the distribution release.
-a, --all
Display all of the above information.
-s, --short
Use short output format for information requested by other options (or version if none).
-h, --help
Display this message.
FILES
If the installation is LSB compliant, the "/etc/lsb-release" file should contain the LSB_VERSION field. The value of the field should be a
colon separated list of supported module versions indicating the LSB specification modules to which the installation is compliant. If the
installation is not compliant, the above field should not be present.
Optional fields are DISTRIB_ID, DISTRIB_RELEASE, DISTRIB_CODENAME, DISTRIB_DESCRIPTION and can be used to override information which is
parsed from the "/etc/distrib-release" file.
If the "/etc/lsb-release.d" directory exists, it is searched for filenames which are taken as additional module-version strings to add to
LSB_VERSION.
The "/etc/distrib-release" file contains a description line which is parsed to get information (especially on currently non-LSB compliant
systems).
The required line style is:
"Distributor release x.x (Codename)"
Where Distributor can be a couple of words, but then concatenated (i.e. Linux Foo BarLinux Linux -> FooBarLinux),
x.x starts with a digit followed by any non-blank characters, Codename will also be concatenated (blanks cleanup only).
release may not be used as a keyword in DISTRIB_DESCRIPTION if you don't want to override "/etc/distrib-release" data.
Notice: To support the Debian distributions' lack of information (see "/etc/debian_version" file) some have been directly added into the
lsb_release script.
EXAMPLES
If the "/etc/lsb-release" file contains:
LSB_VERSION="core-2.0-ia64:core-2.0-noarch"
DISTRIB_DESCRIPTION="I enjoy using my distrib"
and the "/etc/lsb-release.d" directory contains:
graphics-2.0-ia64 graphics-2.0-noarch
and the "/etc/foobar-release" file contains:
My Linux Distrib release 1.0RC4 (TryIt)
Then the results of various options will be:
$ ./lsb_release --all
LSB Version: core-2.0-ia64:core-2.0-noarch:graphics-2.0-ia64:graphics-2.0-noarch
Distributor ID: MyDistrib
Description: I enjoy using my distrib
Release: 1.0RC4
Codename: TryIt
$ ./lsb_release -a -s
1.0 MyDistrib "I enjoy using my distrib" 1.0RC4 TryIt
If the "/etc/lsb-release" file is absent (indicating this is not an LSB compliant distribution), the result will be:
$ ./lsb_release -a
LSB Version: n/a
Distributor ID: MyDistrib
Description: My Linux Distrib release 1.0RC4 (TryIt)
Release: 1.0RC4
Codename: TryIt
REPORTING BUGS
Report bugs at http://bugs.linuxbase.org. Please include a complete, self contained example that will allow the bug to be reproduced, and
say which version of lsb_release you are using.
COPYRIGHT
Copyright (C) 2000, 2002, 2004 Free Standards Group, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Originally written by Dominique MASSONIE.
FSG lsb_release v2.0-SuSE July 2010 FSG(1)