Consider simplification of OS Services Integration

I've run in to several difficult-to-nail-down problems with the currently-in-use "sudo service ..." model on recent Debian and Ubuntu systems-

Doing things this way creates two (needless?) layers of obfuscation where signals and perms are getting dumped/lost: the service command actually executes systemctl, which then through sysv-init simply executes the files in /etc/init.d: appdynamics*

My recommendation is to use these /etc/init.d/appdcontroller* files directly for all operations and exist completely outside of the OS's service management.
IE: we can install those files "/etc/init.d/appdcontroller*" and make sure they work for us and our purposes, and then whatever the OS tries to do with them on startup/shutdown/whatever is its own business.

As it is now, the failover/replicate scripts using "service..." commands results in failure of several operations.