Re: can we stop packaging sysvinit scripts?

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

 



On Wed, 10 Jan 2018, Amon Ott wrote:
> Am 10.01.2018 um 15:44 schrieb Sage Weil:
> > We've had systemd unit files for several releases now and all major 
> > distros are using systemd by default.  Can we stop packaging the sysvinit 
> > scripts?
> > 
> > I realize that Debian allows you to switch init systems... do any users 
> > actually do this?  Is it required that debs include the sysvinit scripts 
> > or is there some glue that lets packages avoid maintaining sysvinit 
> > scripts?
> > 
> > I ask because the init scripts are one of the few remainining bits that 
> > use the ceph-conf utility, which I would like to deprecate (and eventually 
> > remove).  It parses local config files but we are migrating this to the 
> > mon.  We could make ceph-conf pull configs from the mon but I would 
> > like to simplify if possible!
> 
> We would really appreciate having the init scripts around for a long
> while, as we are not willing to use systemd on our servers for security
> reasons. Please do not drop them.

Okay, I think in the end ceph-conf behavior won't change (it will continue 
to only do config files, not mon config) so all of the current users (like 
sysvinit scripts) can continue to do their old legacy thing.  

So... nevermind, I guess!

sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux