| |||||||||||||
The road forward for systemdThe road forward for systemdPosted May 27, 2010 10:00 UTC (Thu) by tzafrir (subscriber, #11501)In reply to: The road forward for systemd by nim-nim Parent article: The road forward for systemd
Have you looked into D-Bus?
(Log in to post comments)
The road forward for systemd Posted May 28, 2010 11:38 UTC (Fri) by nim-nim (subscriber, #34454) [Link]
If your answer is 'you just have to write a new daemon that uses d-bus' that's completely besides the point.
The point is to have an init system able to instanciate existing j2ee servers (certifications, warts and all), either as a system-wide service (production j2ee server) or as per-user instances in the user session (j2ee server instance attached to user ide).
If rewriting with other tech was the answer we'd have java/.net/ruby/whatever OSes by now.
The value of a good init system is too be able to manage existing software gracefully.
The road forward for systemd Posted May 28, 2010 13:56 UTC (Fri) by tzafrir (subscriber, #11501) [Link]
You want those for development time? This should, then, be related to the IDE. Registering them to them system makes it a whole more difficult to debug a single component.
The road forward for systemd Posted May 29, 2010 8:15 UTC (Sat) by nim-nim (subscriber, #34454) [Link]
Nooo
You don't understand
People doing dev want their private daemon that is identical (ports excluded) to the one they will have system-wide in production
As soon as you start changing it so it does not behave like the system one you reduce the whole setup value.
|
|||||||||||||