Re: Whether to use systemd to start services

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Tue, Sep 06, 2016 at 08:03:01PM +0000, Stalker, Tim wrote:
> I'm wondering if it's normally required to start services with
> systemd as opposed to sysv? I currently load a few services using the
> old init.d/service funtionality, which still works fine. Is this ok
> or is sysv going to be fully discontinued in the future? The service
> I load is celeryd via init.d but so far finding few pointers as to
> how to do this with a celery.service file. I can load the service
> with this line execStart=/etc/init.d/celeryd

I don't think there's any plan to remove the sysv init script
compatibility from systemd. That should basically continue to work
forever, and if it's working for you, awesome. 

If you _do_ want to convert a script, there's a nice guide over on Fedora
Magazine:
https://fedoramagazine.org/systemd-converting-sysvinit-scripts/

Why would you want to? You can get some nice functionality like
restart-on-crash behavior or resource limiting with cgroups. But,
again, if you don't wanna, you don't hafta.

-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos



[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux