Hello
I was able to figure this out now - it should be adjusted such that next
time the host bounces, the test service stays offline to conserve
limited memory resources and the production system comes up
automatically.
cheers.
--
Andrew Lindesay
apl@xxxxxxxxxxxxxx
On Thu, May 12, 2016, at 23:28, Axel Dörfler wrote:
Am 12.05.2016 um 13:24 schrieb Andrew Lindesay:
/sbin/insserv failed, exit code 1
Looks like it's calling insserv the wrong way...
Does anybody know how to properly prevent a System-V style service from
starting up on that host?
Don't we have systemd on that system already? If so, I'd rewrite the
service startup to that one.
Since that is the main startup service, it should also definitely work
:-)
Otherwise, you could do chkconfig's job manually, which is just playing
with files and symlinks in the /etc/rc* directories IIRC.
Bye,
Axel.
