Am 11.07.2011 02:49, schrieb Steve Dickson: > My point it this. You are changing the meaning of 'service'. People > expect a service to be just that as service. When one starts a > service all the needed daemons are started and all the configuration > is done once the service is started. > > Unless I'm misunderstanding, for an admin to the same thing as above > the will have to type of string of commands enabling all the needed > daemons... People are not expecting or even what to know which daemon > is need to start up each service... oops.. a service is not longer > as service its a daemon... hmm... let use subsystem... see my point? the same problem with the logic "if there is a svcname.socket" you have to do "systemctl stop svcname.socket svcname.service" or systemd wil fire up it again if you do only "systemctl stop svcname" https://bugzilla.redhat.com/show_bug.cgi?id=714525 nobody would expect this and even if someone knows about this is nothing which makes usabilitöy better lennart please think about such inputs and try to implement logic that your tool does what admins normally expect according to my bugreport (yes the topic was wrong because unexpected bahvior) "systemctl stop mysqld.service" should implicitly always stop an according "svcname.socket" as long we do not restart - STOP means STOP and not restart :-)
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
