Linked by Eugenia Loli on Sun 27th Aug 2006 08:18 UTC
Thread beginning with comment 156419
To view parent comment, click here.
RE[2]: Too ambitious?
by Wrawrat on Sun 27th Aug 2006 22:12 UTC in reply to "RE: Too ambitious?"
Member since:

Actually, jobs would be the proper term, since upstart doesn't make a difference between a task and a service. Furthermore, it will need to supervise these jobs for automatic restarts, logging failures, etc. That's already two things to do...

Given its event-driven nature, I guess it makes sense to replace at and cron. Still, it will need to monitor time. As for inetd, it really depends whether they plan to replace the original version or xinetd... The former would be trivial, the latter would have some complications since it got many complex fetures like access controls (hosts, number of connections, redirection) that doesn't really belong in an init daemon, at least IMO.

All that dynamic & event-driven stuff seem to add a layer of complexity that could be hard to manage. We'll see where this is going to lead, but I'm still skeptical on its impact, especially in performance.

Reply Parent Score: 1