Control: tags -1 + moreinfo On Thu, 4 May 2017 17:47:17 +0200 Christian Hofstaedtler <[email protected]> wrote: > How will a database.target solve anything in those not so uncommon > setups: > > - database is remote > > or > > - one database needs another to start? > > Please consider: if you end up with a solution that only works > for 90% of installations - fails on 10% - is that actually > solving your problem?
I don't understand the use case here. Certainly, in a default apache and mysql configuration, there is no need to delay the start of apache and wait until mysql, mariadb or whatever other db has started (if multiple databases are installed, would we wait for one of them, all of them?) So introducing this artificial delay feels like a regression. If there there is the need to actually start apache after mysql due to how the system is configured for a specific use case, it's very easy to achieve that with systemd by creating a drop-in snippet. To pick up Christian's analogy: If such a database.target is not useful for 90% of its users and actually introduces artificial delays, does this relay outweigh the benefit for those 10% who might benefit from it? I feel like I need better arguments that such a target / synchronization point is a good idea. Especially, how and by which packages such a target should be used (and this would probably need documentation as well) Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
