On Sat, Oct 17, 2009 at 05:52:06AM +0200, Jens Elkner wrote: > Anyway, trying to manage services via PIDs and signals seems to be odd, > especially in the java env because there are even no appropriate methods > to handle them (and that's for reason). And as Nico already pointed out, > every service (not matter which kind of implementation) should provide > a facility to communicate with it and manage it. Doing this by relying > on PIDs (which are at least after a reboot/restart always different) and > sending OS signals to pids is pretty old style fashion and unreliable, > not just because the possebgility to send the sigs to the wrong process > but also because one gets no feedback.
Did I really say that? Certainly management of service enable/disable state should be done via SMF interfaces, though it's OK for the service to have its own interfaces by which users can cause the service to be enabled/disabled, and in some cases this may be highly desirable (e.g., NFS client and server services). But that _every_ service should provide its own interfaces for that? I wouldn't argue that they should. Nico --
