3
votes

For Linux installer, we have added a custom launcher for auto start of service (see pic below). We are using install4j v5.1.6. It creates a link in /etc/init.d/myService.sh which points to the /bin/myService.sh .

It works properly in Ubuntu 13. On system restart, service auto starts properly.

On Ubuntu 14 this doesn't work. Service starts first time after installation. But on system restart, service doesn't auto start.

On further investigation, running these commands on Ubuntu 14 enabled auto start.

   after installation
   cd /etc/init.d
   sudo update-rc.d myService.sh defaults

Under installer, install a service, auto start is set to true. Is this a limitation of install4j that it doesn't register with update-rc.d ? Do we know on which Linux systems copying to /etc/init.d/ is sufficient ?

Our script is similar to : www.shayanderson.com/linux/add-startup-script-or-service-with-linux-on-bootup.htm . What we don't have is update-rc.d and chkconfig. And install4j does the task of copying it to /etc/init.d/

Thanks !

http://s27.postimg.org/o5bih55kz/Launcher_Configuration.png http://s3.postimg.org/icitxy96b/Launcher_Setup.png

1

1 Answers

2
votes

As of 5.1.x, install4j does not integrate services into runlevels, it only creates the symlink to the start script in /etc/init.d.

Integrating it into runlevels has to be done manually, such as by calling update-rc.d or whatever other tool the particular distribution provides.