DB2 uses this line in /etc/inittab to autostart and monitor DB2 database instances:
fmc:2345:respawn:/opt/ibm/db2/V10.1/bin/db2fmcd #DB2 Fault Monitor Coordinator
This does no longer work with openSUSE standard system with systemd startup because systemd does not use /etc/inittab at all.
Could someone please tell me how to get that functionality with systemd?
I mean, including correct time of first start, respawning, errorhandling with start delays, not starting in runlevel 1, environment, signalhandling, …
I looked at the getty replacement /lib/systemd/system/getty@.service and it looks like a good starting point, But I am lost at the details.
I mean its a long way from
[Unit] Description=Getty on %I BindTo=dev-%i.device After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service # If additional gettys are spawned during boot then we should make # sure that this is synchronized before getty.target, even though # getty.target didn't actually pull it in. Before=getty.target [Service] Environment=TERM=linux ExecStart=-/sbin/agetty %I 38400 Restart=always RestartSec=0 UtmpIdentifier=%I TTYPath=/dev/%I TTYReset=yes TTYVHangup=yes TTYVTDisallocate=yes KillMode=process # Unset locale for the console getty since the console has problems # displaying some internationalized messages. Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE= LC_MEASUREMENT= LC_IDENTIFICATION= # Some login implementations ignore SIGTERM, so we send SIGHUP # instead, to ensure that login terminates cleanly. KillSignal=SIGHUP [Install] Aliasfirstname.lastname@example.org