Am 10.02.2012 19:18, schrieb Chris Adams: > Once upon a time, Reindl Harald <h.reindl@xxxxxxxxxxxxx> said: >> i have rpeorted A TON of bugs where services was not converted to systemd >> many of them are also not converted until now > > Are you doing this because there is a functionality problem? Systemd is > explicitly (mostly) backwards compatible with SysV-style init scripts, > because they are going to exist for a long time to come (at least in > third-party and vendor packages). IIRC, systemd was introduced without > any mandate to switch 100% of the init scripts. it is proven that it is only MOSTLY comatible and you can https://bugzilla.redhat.com/show_bug.cgi?id=714426 only the egg-dance around mysqld shows that it was wrong to bring in systemd without enforce convertig, read the bugreport carefully so you may understand that half of the time nobody knew how to do with systemd currently nobody knows how much services are only working in default configurations and with luck since the order of start/stop is onot always the same nobody knows what sevices are hardly or not conertable currently because nobody tried it and in the worst case if oyu start you find out missing features / design problems in systemd which can only be cleaned up while systemd-debelopers working hand in hand with packagers what did and does not happen, and even if it happens now it is way too late and should have been done BEFORE release it as feature it is proven not comatible because since F15 reboot/shutdown a machine running VMwareWorkstation geusts leads in kill them hard instead suspend and i spent many time to try services before "vmware" to suspend which is all working ina dry run but if you call reboot the cmware-service is stopped too soon and my only explaination is that systemd is designed for doing things fast but not safe!
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
