Suse 2.6.27.48 giving insserv: warning: script ‘S12ITMAgents30’ missing LSB tags and overrides, there are few more similar type of warning on adding the new init script but the Suse 2.6.16.60 is not giving any error on using the same init script.
On 2011-04-11 09:36, chinagrawal wrote:
>
> Suse 2.6.27.48 giving insserv:
There is no such thing as Suse 2.6.27.48
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Hi Carlos,
thanks for the reply. 2.6.27.48 is the kernel version. I am using suse11. Missing LSB tag warning is coming at kernel version 2.6.27.48 but no warning on Suse kernel version 2.6.16.60.
You can add the missing LSB tags to the scripts if it’s bothering you. I wrote a function to do that. I use it sometimes with 3rd party scripts. Normally the ones in openSUSE are supposed to be LSB compliant.
function lsb {
for iscript in `find /etc/init.d -maxdepth 1 -type f -executable ! -name "*.local" ! -name "*.orig"` ; do
-f ${iscript}.orig ] && continue
grep -q '### BEGIN INIT INFO' $iscript && continue
case $(basename $iscript) in
single|halt|powerfail|rc|boot) continue ;;
*)
cp $iscript{,.orig}
echo "- making $iscript LSB compliant"
s=$(basename $iscript)
sed -n '1,/^^# ]/p' $iscript.orig | sed '$d' > $iscript
cat >> $iscript << EOFLSB
# LSB compliant service control script
#
### BEGIN INIT INFO
# Provides: $s
# Required-Start: \$remote_fs \$all
# Should-Start:
# Required-Stop:
# Should-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: $s
# Description: Starts and stops $s
### END INIT INFO
EOFLSB
sed -n '/^^# ]/,$p' $iscript.orig >> $iscript
;;
esac
done
}
Thanks for reply. But my question is why it is coming on some Suse machine not on other Suse machines.
On 2011-04-11 16:06, chinagrawal wrote:
>
> Hi Carlos,
> thanks for the reply. 2.6.27.48 is the kernel version. I am using
> suse11.
There is no openSUSE 11 either - so you may be using the enterprise
version, SLES or SLES 11, and in this case, this is the wrong forum.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Just look at this file and you’ll see if the LSB tags are missing. If so, just add them (the part of my post between #BEGIN INIT INFO and #END INIT INFO (remove the backslash before $ and replace $s with the service name.)
The answer why these tags are missing is that the init script is ‘buggy’ in some way. The reason why some systems complain and other don’t is that some do a LSB check and other not.