On 02/16/2013 01:13 AM, Adam Williamson wrote:
On 15/02/13 02:15 PM, "Jóhann B. Guðmundsson" wrote:
On 02/15/2013 09:12 PM, Honza Horak wrote:
On 02/15/2013 03:13 PM, "Jóhann B. Guðmundsson" wrote:
On 02/15/2013 12:52 PM, Honza Horak wrote:
There is no change, the unit file is still mysqld.service.
Hmm..
It's probably better to have an mariadb own unit files and create
corresponding mysql symbolic link to those unit files for backwards
compatibility at install time.
( we already do so at few places to keep backwards compatibility with
the service command to systemd units in few places )
I don't understand what would be the benefit, except that the files
wouldn't conflict, but the packages conflict anyway currently.
User expectations as in if you install something called mariadb then
it's expected that you start the service via systemctl start
mariadb.service ( or service mariadb start ).
Either way, we don't need symlinks, do we? systemd already lets you
set aliases.
Sorry not following alias are symlinks as in all systemctl does is to
run it when you enable it
ln -s '/etc/systemd/system/foo.service' '/etc/systemd/system/bar.service'
It even says so when you run that command
They are not without their flaws as in you have to enable the unit first
before you can use it as in the alias cant be used until you enable it
first [Install] remember so neither systemctl or service commands work
on the alias in the above example bar until you do =)
And you cant disable alias ( which probably is a bug I should have filed
long ago )
JBG
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
