05-02-2012
/etc/profile is often a complicated script, is the thing, so using it may be somewhat overkill, not to mention, might do something unexpected when used non-interactively.
9 More Discussions You Might Find Interesting
1. Red Hat
I'm trying to install Redhat LInux AS 4 update 4 on an IBM x306 series server. I keep getting following error:
"No Drives Found. An error has occurred - no valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem."
I called IBM and... (2 Replies)
Discussion started by: pieman8080
2 Replies
2. Shell Programming and Scripting
hi all,
here i am trying to run one control file.
but getting "-bash: sqlldr: command not found" error :confused:
the code is given below.
sqlldr $db_username/$db_password@$db_sid control=$loading_path/load_to_table.ctl log=loading.log
can anybody help me in fixing the issue?
... (1 Reply)
Discussion started by: vinayakatj56
1 Replies
3. Post Here to Contact Site Administrators and Moderators
Hi,
Today, I've submitted a new tread in "Shell Programming and Scripting" forum, with title "-bash: ELF: command not found ". However, this thread has disappear.
Can somebody give me an explanation?
Regards. (3 Replies)
Discussion started by: Sonia_
3 Replies
4. Red Hat
Hi All
I would like to profile my application with oprofile but I can't since no samples are collected.
The kernel of my app is 2.6 on RED HAT Enterprise 5.3 (Tikanga) so OProfile is setup in timer interrupt mode
# opcontrol --list-events
Using timer interrupt.
I... (0 Replies)
Discussion started by: manustone
0 Replies
5. Shell Programming and Scripting
i=0
numberofproducts=${#urls} #gets number of entries in array called "urls"
numberofproductsminusone=`expr $numberofproducts - 1` #-subtract by one
while
do
wget ${urls}
i=$(( $i + 1 ))
sleep 10
done
I'm getting an error
./scrape: line 22: [0: command not found
that... (3 Replies)
Discussion started by: phpchick
3 Replies
6. Shell Programming and Scripting
Hello Geeks,
Greetings...I have the following script:
#!/usr/bin/bash
#Script to generate number of active PDP context & calculate PDP activation #failurefrom EPG-M
#Script written by Gbenga Adigun
#September 12, 2013
username="xxxxxx"
password="xxxxxxxxx"
HOSTS=(
ggsn01... (6 Replies)
Discussion started by: infinitydon
6 Replies
7. Shell Programming and Scripting
Hello everyone,
I am having problems figuring this out.
This script below is supposed to create a list of file names with their "md5sum", in a file "lib-list.txt"
When I run it "sh component-list.sh " I get this:component-list.sh: 4: component-list.sh: function: not found
component-list.sh:... (4 Replies)
Discussion started by: joemb
4 Replies
8. UNIX and Linux Applications
Hi all,
i face an error related to my server ""it's running server"" when i use sqlplus command
$ sqlplus
bash: sqlplus: command not found
the data base is up and running i just need to access the sqlplus to import the dump file as a daily backup.
i already check the directory... (4 Replies)
Discussion started by: clerck
4 Replies
9. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
LEARN ABOUT NETBSD
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)
NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS
--help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO
lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN
Debian Utilities CHECKBASHISMS(1)