problems omsa 5.2 debian installation

[Sean Finney]

hi, (excuse the gross top-posting, i'm using a crappy MUA today...)

if the problem is using a non-bash shell as the /bin/sh equivalent, then
the init script should not call "#!/bin/sh" and instead call "#!/bin/bash".
making a major system change to fix one broken init script seems just... wrong :)

but regardless, it looks to me like the problem is that someone has appended the string "custom" to a pre-existing version string, which was assumed to be numeric previously.

i.e. there's probably something like:

version=`somecmd --version | maybe some sed to get the minor part`
if [ "$version" -lt "123" ]; then
   do something
fi

an easy fix without having to change much would thus be to add something to the above pipe
kinda like:

version=`somecmd --version | tr -dc '[0-9]' | maybe some sed to get the minor part`

of course this is all speculation without even having looked at the init script in question...


    sean

----- Original Message -----
From: Andrew Reid <AndrewReid at eastlink.ca>
Sent: Mon, 7/2/2007 2:04pm
To: tere <tfinez at etsetb.upc.edu>
Cc: Linux Dell List <linux-poweredge at lists.us.dell.com>
Subject: Re: problems omsa 5.2 debian installation

tere wrote:
> hi! I've found some problems trying to install omsa 5.2 with debian
> package from SARA. When it tries to install it says:
> 
> 
> Loading kernel modules
> Starting Systems Management Device Drivers:
> Starting ipmi driver: /etc/init.d/instsvcdrv: line 426: [: 19custom:
> integer expression expected
> /etc/init.d/instsvcdrv: line 431: [: 19custom: integer expression expected
>                                                            [FAILED]
> Starting dataengine
> Starting Systems Management Device Drivers:
> Starting ipmi driver: /etc/init.d/instsvcdrv: line 426: [: 19custom:
> integer expression expected
> /etc/init.d/instsvcdrv: line 431: [: 19custom: integer expression expected
>                                                            [FAILED]
> 
> 
> Can help me anyone? Thanks
> 

As previously reported on the list, make sure you are running bash as 
your sh equivalent. The script (/etc/init.d/instsvcdrv) has several 
"bashism" and does not play well with dash, ash etc.


sh --version should tell you what you are running.

If it is NOT bash, the exact mechanism to use bash as the sh replacement 
is a matter of preference, the quickest is a soft link in /bin (mv 
/bin/sh /bin/bad-sh; ln -s /bin/bash /bin/sh) or the debian way 
dpkg-reconfigure bash.

If it is bash, let us knw what the real problem was.



_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq