Rudder

On a SLES12 SP2 system after the initial installation of the agent 4.1.3:

vm00049:/home/cloud # rudder agent start
rudder-agent is neither service nor target!?
error: start service rudder-agent failed

This is because /sbin/service rudder-agent start is determined as default to be called by service_action:

if [ -x /usr/sbin/service ]; then
  CMD="service ${service} ${action}" 
elif [ -x /etc/init.d/${service} ]; then
  CMD="/etc/init.d/${service} ${action}" 
elif [ "${action}" = "start" ] && [ -x /usr/bin/startsrc ]; then
  CMD="startsrc -s ${service}" 
elif [ "${action}" = "stop" ] && [ -x /usr/bin/stopsrc ]; then
  CMD="stopsrc -s ${service}" 
fi

However, service does use systemd (at least in sles12 sp2):

vm00049:/home/cloud # bash -x /sbin/service rudder-agent status                      
...
+ is_service rudder-agent
++ systemctl --full --no-legend --no-pager --type=service --property=LoadState show rudder-agent.service
+ local state=LoadState=not-found
+ test LoadState=not-found = LoadState=loaded
+ is_target rudder-agent
++ systemctl --full --no-legend --no-pager --type=target --property=LoadState show rudder-agent.target
+ local state=LoadState=not-found
+ test LoadState=not-found = LoadState=loaded
+ echo 'rudder-agent is neither service nor target!?'
rudder-agent is neither service nor target!?
+ return 1