System V issues
system V has some drawback such as init scripts don’t automatically respawn if the service dies.
another issue is that init scripts are only affected by changes in runlevel and when a system starts up but are otherwise not executed unless you do so manually
EX: init scripts that depend on network connectivity. on red hat or debian based systems an init script called network or networking establishes the network connection. any init script that depends on a network connection are named with a higher number than this init script to ensure they run after the the network script has run.
if the network cable was unplugged then the network script would run but all the init scripts that need network connectivity would time out one by one. you could plug the cable back in and restart networking but the other service that needed network connectivity would not restart. you would have to manually restart them.
Last updated
Was this helpful?