> On 17 May 2016, at 08:25, Fred Liu <fred.f...@gmail.com> wrote: > > 2016-05-17 15:10 GMT+08:00 Chris Ridd <chrisr...@mac.com>: >> >>> On 17 May 2016, at 07:40, Fred Liu <fred.f...@gmail.com> wrote: >>> >>> 2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>: >>>> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote: >>>>> I have no success to boot the system V init scripts. >>>>> Any success here? >>>> >>>> Can you give us a bit more detail about what you're doing? Is this a >>>> custom script you have added to your machine? Is it in the global >>>> zone of your SmartOS host, or in a SmartOS or LX-branded zone? At >>>> what path did you install the file? >>>> >>>> >>>> Cheers. >>>> >>> >>> We are running (CentOS 6.7 20151005) LX Brand. It is a custom script. >>> I installed it on /etc/init.d/iqs. It is just a simple sh script: >> >> Add “set -x” near the start of the script and find out where it is failing. >> > > It can be started manually with no problems. > The issue it can't be automatically started when we reboot LX Brand. > Because the boot process is totally different in LX Brand. > So the question converts to how to debug the boot process in LX Brand.
OK, that’s some useful extra detail. Does something even *try* to run your script? Have you used chkconfig to enable it for the right Linux run levels? Maybe the LX zone isn’t in the run level you think it is. I would have thought that set -x could still be helpful if the output is captured in a system log which you can look at later. (I don’t recall what Linux does.) Or echo something into a tmp file, and see if that gets written during the boot. Chris ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
