08-17-2011
Ok. Maybe sometimes there is magic.
On Linux box this script works without any problems. And yes it's simple and there are not any typos.
As you can see I don't believe in magic so my fantasy is very limited. I couldn't suggest what may happen. :-(
---
Some crazy thought - may be you ran your script from "cmd" window with cmd as shell? Or from GUI?
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
When i run sh -x test.sh, expr outputs x=expr $x + 1 instead of doing the arithmetic.. been working on this overnight.. and its being a pain in the arse if you ask me.. :confused::confused:
#!/bin/sh
#script for downloading numerical filenames
chap=1
p=1
count=0
x=1
while
do
if ... (2 Replies)
Discussion started by: aspect_p
2 Replies
2. Shell Programming and Scripting
script outputting cant find anything wrong with the script either... :
#!/bin/sh
#count execution script
time=0
while
do
if
then
time=`expr $time + 1`
if
then
echo "The current tick is 100"
fi
fi (2 Replies)
Discussion started by: aspect_p
2 Replies
3. Shell Programming and Scripting
I'm trying to take a list of domains, find out the MX resolve it to IP then find out what the NS is and output the contents to a new file.
The only problem i'm having is when checking the Ip or host of the MX i can only get it to print the column with the MX record and the results of the host... (1 Reply)
Discussion started by: spartan22
1 Replies
4. Shell Programming and Scripting
Howdy all, I have a scritp that does a sqldump. But for some goofy reason, a certain part of it behaves uber strange.
It does a daily dump of my sql, according to parameters I enter in hardcode.
The script is:
#!/bin/bash
APP_NAME="app_com_site"
wikiname="wiki_com_site"
... (8 Replies)
Discussion started by: saariko
8 Replies
5. Shell Programming and Scripting
Hi all,
I have a requirement to create a "superset" file out of a number of different sources with some different and some same columns.
We intend to have a manually updateable SuperSetCols.csv which would look like
"ColA","ColB","ColC","ColD","ColE","ColF","ColG"
so someday we may add... (3 Replies)
Discussion started by: Leedor
3 Replies
6. UNIX for Dummies Questions & Answers
I need to enable set -x in my croned script as at times the script is not returning all data that it should be. This only happens intermittently and as such I would like a means of being able to check what goes wrong.
My question is how to output the debug of set -x to file? (1 Reply)
Discussion started by: rob171171
1 Replies
7. Shell Programming and Scripting
Hello All,
I am learning BASH scripting and I would appreciate any help with a small problem I am having...
I am writing a script that builds a simple hosts file for DNS reasons related to a piece of software called netdb by parsing another application's config files for IP's and their... (4 Replies)
Discussion started by: Wesley545
4 Replies
8. Shell Programming and Scripting
Hi,
I want to check the incoming files whether the file is Mac file or dos/windows file in unix shell script.
Sometimes client is posting Mac file and sometimes it is dos file. Could you please help me how to determine/check whether the file is Mac or dos.
Help in advance
Thanks (4 Replies)
Discussion started by: lkeswar
4 Replies
9. Shell Programming and Scripting
Hello,
I work in Ubuntu 16.04, I am new to Bash and something is wrong with my script, please help.
I have a few hundreds of subjects data (like subj003.nii.gz, subj012.nii.gz etc. up to subj567.nii.gz) in a directory /usr/afewmoredirectories/subjects.
I may run for each subject a command... (5 Replies)
Discussion started by: lim-lim
5 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)