On Jun 12, 2015, at 16:49 45, Rob Landry <[email protected]> wrote:
> The old System V init mechanism works fine; why mess with it? From “The Upstart Intro, Cookbook and Best Practices” guide, section 3.1.2.1.1 [http://upstart.ubuntu.com/cookbook/upstart_cookbook.pdf]: *** snip snip *** In the days of colossal Unix systems with hundreds of concurrent users, where reboots were rare, the traditional SysV approach was perfect. If hardware needed replacing, a system shutdown was scheduled, the shutdown performed, the new hardware was installed and the system was brought back on-line. *** snip snip *** While I’m not sure that I’d describe any Rivendell system as ‘colossal’, the rest of the description fits the typical Riv system to a T. By the Upstart developers own admission, the SysV setup is ‘perfect’ for that environment. So indeed, why mess with it? Cheers! |----------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |----------------------------------------------------------------------| | A room without books is like a body without a soul. | | -- Cicero | |----------------------------------------------------------------------| _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
