Xymon Mailing List Archive search

error on script

list Vernon Everett
Mon, 12 Dec 2011 06:28:16 +0800
Message-Id: <user-ea1e29c85035@xymon.invalid>

I remember bumping into this one some time back.
I cannot remember how I fixed it - although I have vague recollections of
modifying it to suite my ksh version.
That was about 5 or 6 contracts ago, so I no longer have the code, but I
think I did pass it on to somebody on the list.

There is also a remake of bb-moracle on the Xymonton web page. It looks
like it needs sh, making it a little more portable.
Why not check if that will suit you needs?

Regards
     Vernon


On 10 December 2011 23:44, Gore, David W (David) <user-368fd67cc6bd@xymon.invalid>wrote:
It may be important to keep in mind the different versions of Korn shell.
 I cannot remember which script assumed that I had ksh93 which wasn't the
version installed on our Solaris machines, maybe it was AIX or HPUX who
knows. So it caused errors that could only be resolved by knowing the
differences and how to resolve those differences between the older and
newer versions of Korn shell.  Regardless, although it took me some time to
understand some database details, dbcheck.pl seemed to be a better tool
that you can run from the Xymon server.


~David

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf
Of user-ce4a2c883f75@xymon.invalid
Sent: Wednesday, December 07, 2011 07:37
To: Sailesh
Cc: xymon at xymon.com
Subject: Re: [Xymon] error on script

On Wed, 7 Dec 2011 12:08:54 +0400, "Sailesh"
<user-603c06b12dd1@xymon.invalid> wrote:
I have an script for checking my database. I am getting an error but I
am
unable to trouble shoot.

/xymon/client/ext/bb-roracle.ksh[58]: (VAR0+=2),(VAR1+=2): syntax error
/xymon/client/ext/bb-roracle.ksh[58]: (VAR0+=2),(VAR1+=2): syntax error
bash-3.00#
The script appears to use the Korn Shell (ksh), so you'll have to install
that for it to work. From the command prompt, it seems you are running
Bash.

On Linux, you can usually install the "ksh" or "pdksh" packages to get a
working ksh. And make sure the first line of the script points to your
"ksh" binary, like

 #!/bin/ksh

if it is installed in /bin


Regards,
Henrik

-- 
"While it is futile to try to eliminate risk, and questionable to try to
minimize it, it is essential that the risks taken be the right risks. "
- Peter F. Drucker