Fixed
Created: Jan 29, 2014
Updated: Mar 11, 2016
Resolved Date: Feb 18, 2014
Found In Version: 5.0.1.10
Fix Version: 5.0.1.12,5.0.1.14
Severity: Critical
Applicable for: Wind River Linux 5
Component/s: Userspace
After building the ovp-ovirt-node the created rootfs contains:
ahedlund@arn-build2:/opt/ahedlund/proj/wrl/build_ovirt-node_rcpl10/export/dist/etc/rc6.d$ ls -l S*
lrwxrwxrwx 1 ahedlund users 18 Jan 21 14:51 S20sendsigs -> ../init.d/sendsigs
lrwxrwxrwx 1 ahedlund users 21 Jan 21 14:51 S25save-rtc.sh -> ../init.d/save-rtc.sh
lrwxrwxrwx 1 ahedlund users 22 Jan 21 14:51 S31umountnfs.sh -> ../init.d/umountnfs.sh
lrwxrwxrwx 1 ahedlund users 17 Jan 21 14:51 S32rpcbind -> ../init.d/rpcbind
lrwxrwxrwx 1 ahedlund users 18 Jan 21 14:51 S40umountfs -> ../init.d/umountfs
lrwxrwxrwx 1 ahedlund users 16 Jan 21 14:51 S90reboot -> ../init.d/reboot
This is fine.
However, after deploying, booting and installation by oVirt engine I see the following:
root@ovirt-node:/etc/rc6.d# ls -l S*
lrwxrwxrwx 1 root root 16 Jan 24 13:41 S50reboot -> ../init.d/reboot
lrwxrwxrwx 1 root root 17 Jan 24 13:41 S50rpcbind -> ../init.d/rpcbind
lrwxrwxrwx 1 root root 21 Jan 24 13:41 S50save-rtc.sh -> ../init.d/save-rtc.sh
lrwxrwxrwx 1 root root 18 Jan 24 13:41 S50sendsigs -> ../init.d/sendsigs
lrwxrwxrwx 1 root root 18 Jan 24 13:41 S50umountfs -> ../init.d/umountfs
lrwxrwxrwx 1 root root 22 Jan 24 13:41 S50umountnfs.sh -> ../init.d/umountnfs.sh
All S* links has been renamed to S50xxxx!
I'm not sure what part of the SW make this terrible renaming but it's causing a lot of problems as "reboot" will be run first and not last.
The same problem exists for the S* links under /etc/rc0.d/.
Add a chkconfig tag to the init scripts:
cat /etc/init.d/reboot
#!/bin/sh
# chkconfig: 23456 90 90
Info:
he first value ’2345' states the default runlevels at which the service should be started. In this case, the service is configured to start at runlevel 2,3,4 & 5.
The second value ’55' states the start priority of the service. In this case the sshd service shall be started after starting all those services having start priority less than 55.
The third value ’25' states the stop priority of the service. In this case the sshd service shall be stopped after stopping all those services having stop priority less than 25.
http://www.thegeekscope.com/linux-chkconfig-configurations-in-init-d-scripts/
1) Build an ovp-ovirt-node platform project (preferably using a product installation).
2) Deploy and boot the ovp-ovirt-node on target.
3) At some stage the S* links under /etc/rc6.d/ and /etc/rc0.d gets renamed to S50xxxx.
