Issue

• A startup script for the third party application doesn't run on system boot.

# ll /etc/rc.d/rc3.d

[...]

lrwxrwxrwx. 1 root root 15 Dec  3  2013 S25netfs -> ../init.d/netfs
lrwxrwxrwx. 1 root root 19 Dec 12  2013 S26haldaemon -> ../init.d/haldaemon
lrwxrwxrwx. 1 root root 20 Mar 14 18:55 S26hypervkvpd -> ../init.d/hypervkvpd
lrwxrwxrwx. 1 root root 19 Dec  3  2013 S26udev-post -> ../init.d/udev-post
lrwxrwxrwx. 1 root root 16 Mar  4 16:39 S28autofs -> ../init.d/autofs
lrwxrwxrwx. 1 root root 15 Mar 14 18:55 S50kdump -> ../init.d/kdump
lrwxrwxrwx. 1 root root 17 Mar 14 18:55 S50mcelogd -> ../init.d/mcelogd
lrwxrwxrwx. 1 root root 14 Dec  3  2013 S55sshd -> ../init.d/sshd
lrwxrwxrwx. 1 root root 16 Dec 12  2013 S60vsftpd -> ../init.d/vsftpd
lrwxrwxrwx. 1 root root 17 Dec  3  2013 S80postfix -> ../init.d/postfix
lrwxrwxrwx. 1 root root 19 Feb  5  2014 S82abrt-ccpp -> ../init.d/abrt-ccpp
lrwxrwxrwx. 1 root root 15 Feb  5  2014 S82abrtd -> ../init.d/abrtd
lrwxrwxrwx. 1 root root 19 Feb  5  2014 S82abrt-oops -> ../init.d/abrt-oops
lrwxrwxrwx. 1 root root 13 Dec 17  2013 S84ksm -> ../init.d/ksm
lrwxrwxrwx. 1 root root 18 Dec 17  2013 S85ksmtuned -> ../init.d/ksmtuned
lrwxrwxrwx. 1 root root 15 Dec  3  2013 S90crond -> ../init.d/crond
lrwxrwxrwx. 1 root root 18 Dec 17  2013 S95virt-who -> ../init.d/virt-who
lrwxrwxrwx. 1 root root 18 Jan 18  2014 S97libvirtd -> ../init.d/libvirtd
lrwxrwxrwx. 1 root root 15 Dec  3  2013 S97rhnsd -> ../init.d/rhnsd
lrwxrwxrwx. 1 root root 19 Dec  3  2013 S97rhsmcertd -> ../init.d/rhsmcertd
lrwxrwxrwx. 1 root root 19 Mar 14 16:51 S99firstboot -> ../init.d/firstboot
lrwxrwxrwx. 1 root root 24 Jan 18  2014 S99libvirt-guests -> ../init.d/libvirt-guests
lrwxrwxrwx. 1 root root 11 Dec  3  2013 S99local -> ../rc.local
lrwxrwxrwx. 1 root root 19 Mar 14 16:51 S99someapplication -> /opt/someapplication <<<<<<<<<<<<<<<< This application doesn't start up on boot.

• When I run the startup script with service command manually, it works fine and the application starts.

• I added -x option in the first line in the application's startup script to find some problem that prevented it from starting up on system boot:

#!/bin/sh -x

[...]

• However, looking at the boot.log, it looks like rc doesn't so much as try to run the application's startup script on boot as shown below:

[...]

Starting cups:                                             [  OK  ]
Mounting filesystems:                                      [  OK  ]
Starting HAL daemon:                                       [  OK  ]
Retrigger failed udev events                               [  OK  ]
Starting PC/SC smart card daemon (pcscd):                  [  OK  ]
Starting snmpd:                                            [  OK  ]
Starting sshd:                                             [  OK  ]
Starting vsftpd for vsftpd:                                [  OK  ]
Starting postfix:                                          [  OK  ]
Starting crond:                                            [  OK  ]
Starting atd:                                              [  OK  ]
Starting rhsmcertd...                                      [  OK  ]

• How do I work on this problem to identify the cause of the application's startup script not being run on system boot?