The latter is also the reason why commands used during the installation of Gentoo Linux used script takes care of the initialization, so one might say that init doesn't do much - it delegates the task of initializing the system to another process.
Second, init executed all scripts that had symbolic links in l0:0:wait:/sbin/openrc shutdown l1: S1:wait:/sbin/openrc single l2:2:wait:/sbin/openrc nonetwork l3:3:wait:/sbin/openrc default l4:4:wait:/sbin/openrc default l5:5:wait:/sbin/openrc default l6:6:wait:/sbin/openrc reboot c345:respawn:/sbin/agetty 38400 tty1 linux c345:respawn:/sbin/agetty 38400 tty2 linux c345:respawn:/sbin/agetty 38400 tty3 linux c345:respawn:/sbin/agetty 38400 tty4 linux c345:respawn:/sbin/agetty 38400 tty5 linux c345:respawn:/sbin/agetty 38400 tty6 linux In a previous section, we saw that init uses a numbering scheme to decide what runlevel it should activate.
Am I missing something with update-rc.d or LSB to get this configured?
I won't recommend trying to make this work, especially since it would have taken you far less time to write the systemd unit file than you've already spent on this.[Unit] Description=Apache Solr After=syslog.target network.target remote-fs.target nss-lookup.target [Service] Type=simple Environment File=/etc/courtlistener Working Directory=/usr/local/solr/example Exec Start=/usr/bin/java -jar -server -Xmx$ -DINSTALL_ROOT=$ Restart=on-failure Limit NOFILE=10000 [Install] Wanted By=multi-user.target I had the same error while trying to use a LSB init script on Cent OS 7.
Root cause turned out to be that the script was a symbolic link.
runlevel is one of the runlevels supported by init, namely, 0123456789S, and NN is the two-digit sequence number that determines where in the sequence init will run the scripts.
Please note that this program was designed for use in package maintainer scripts and, accordingly, has only the very limited functionality required by such scripts.