В Mon, 19 Jan 2015 18:19:11 +0100 Christian Boltz <opensuse@cboltz.de> пишет:
Hello,
Am Montag, 19. Januar 2015 schrieb Marcus Meissner:
On Sun, Jan 18, 2015 at 10:47:26PM +0100, Christian Boltz wrote:
Am Samstag, 17. Januar 2015 schrieb Tomáš Chvátal:
* There was promise that inits will keep working
- there was promise that systemd will run initscript for external
stuff so you keep compatibility and can in the case still run your software. That compat is not going away and actually we really really really want it to be around for a long time.
Oh really?
https://bugzilla.opensuse.org/show_bug.cgi?id=853019 (non-public, sorry) is about a compability problem that is even security-relevant. I reported it a year ago, and nobody did anything to fix it :-( Incorrect. I at least tried to think of a solution but did not get to any.
Unfortunately, thinking about it doesn't fix it :-( Besides that - please don't try to destroy a nice rant with facts ;-)
Seriously: I can think of an easy and obvious solution - the wrapper should just hand over the parameter it gets to the initscript without any modification. This means: systemctl foo restart -> /etc/init.d/foo restart
systemd does not have notion of "restart" as first class citizen. It implements "restart" as "stop" followed by "start".
instead of the current, broken behaviour
All initscripts I am aware of implement "restart" as "stop" followed by "start". I very seriously doubt anyone will spend time for the sake of single script that decided to interpret it differently. May be this script actually misuses "restart" for "reload" here? I'm guessing - bug is non public ...
systemctl foo restart -> /etc/init.d/foo stop ; /etc/init.d/foo start
I know that sounds too easy ;-) I don't know the wrapper code so I can only hope and assume that it really _is_ that easy for someone who knows the code.
I'm looking forward for an answer from someone more familiar with systemd ;-)
I opened the bugreport.
Ah, OK. As I suspected: restart|reload|force-reload) "When I use a word," Humpty Dumpty said, in rather a scornful tone, "it means just what I choose it to mean—neither more nor less." I guess, the obvious answer is - do not use %restart_on_update boot.apparmor in spec file, explicitly use "systemctl reload". We obviously have service whose behavior is very different to others, so it is logical to deviate from defaults.
Thanks, that makes sense after it was discussed in public.
Regards,
Christian Boltz
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org