On 06/01/12 17:45, Brian K. White wrote:
You continue to ignore problems that don't interest you.
Well, yeah, problems that do not interest me will likely be addressed by someone else.
stating that they are invalid without demonstrating how or why.
It is not up to me to demostrate that.
When people say "how do I do this with systemd" that is not an empty question, and requires an non-empty answer.
The documentation answers most if not all of the questions.
I believe I have demonstrated enough understanding of my particular top problem by suggesting that at least one way to get a service (such as container-based vm's) that don't employ a constant daemon, but never the less do have a start action, a stop action, and a status action, is by adding a watchdog process that will serve as the always-running daemon process that systemd can then watch the way it expects to, and would perform those same actions that the init script currently does.
You are fooling yourself, you are entitled to believe that sysv scripts do what you want, but that does not make it true why ? in sysvinit processes escape the init system, and control cannot be regained. It may tell you that it is working or running, when it is not or is running under a different PID, there is no way to "contain" them, hence no way to determine in a reliable way if what "status" says is true.
Now, if I'm wrong, and there IS a way to get all the proper functionality and behavior via systemd that I currently enjoy via sysv init, it is YOUR OBLIGATION.
NO, I dont have any obligation, I am a volunteer, I do what I can or what I care about.
as the person who is trying to inflict such a disruptive change to such a long-standing core part of the system, to provide the drop-in systemd replacement.
I am not trying to inflict anything ... people always can choose something else or keep maintaining other init systems if they have interest or skills, anyone can step up to the task of taking care of this legacy systems, lots of luck with that. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org