Background Services and systemd

systemd now manages background services daemons on CentOS.

This feature was suggested and voted up by users on the Flame Feedback portal.

systemd now manages background services daemons on CentOS.

Flame Family products use many scripts started at workstation startup for the various background services. Previous version of Flame Family products used initd to manage these services. Flame Family 2022 changes that to use systemd, a modern and more flexible service manager.

The following scripts have migrated to systemd:

• Backburner

• Backbuner servers

• Backburner Manager

• WiretapGateway

• Stone+Wire

• dlmpd

• Lustre Shot Reactor

Using systemd changes how you can interact with the services:

• System Monitor—System Monitor works systemd or initd depending of what is installed. Since only 2022 services have been updated to systemd, legacy services are still managed by initd.
• Command line tools—If you prefer interacting with the background services with the command line, know there is an almost one-to-one match between systemd and init.d.

initd command	sytemd matching command
/etc/init.d/stonewire (start|stop|restart)	/bin/systemctl (start|stop|restart) adsk_sw
/etc/init.d/backburner (start|stop|restart)	/bin/systemctl (start|stop|restart) adsk_backburner
/etc/init.d/backburner_manager (start|stop|restart)	/bin/systemctl (start|stop|restart) adsk_backburner_manager
/etc/init.d/backburner_server (start|stop|restart)	/bin/systemctl (start|stop|restart) adsk_backburner_servers
/etc/init.d/wiretapgateway (start|stop|restart)	/bin/systemctl (start|stop|restart) adsk_wiretapgateway
/etc/init.d/dl_mpd_manager (start|stop|restart)	/bin/systemctl (start|stop|restart) adsk_dl_mpd
/etc/init.d/lustre_shot_reactor_<version> (start|stop|restart)	/bin/systemctl (start|stop|restart) adsk_lustre_shot_reactor_<version>

To get the status of a service:

• /bin/systemctl status adsk_wiretapgateway

To get the status of more than one service, use wilcards:

• /bin/systemctl status "adsk_*"

• /bin/systemctl status "adsk_sw_*"

Important: Getting background services logs—systemd is the parent process of the daemon, not the shell where the command is done. This means that the stdout and stderr of the service are routed to the system logs. To access the logs, use the command journalctl.

#To access the latest error logs:
/usr/bin/journalctl -xe