On Thu, Sep 28, 2017 at 04:27:31PM -0500, Austin English wrote: > (Note: serious discussion, please take systemd trolling elsewhere). > > While having the pleasure of working with some proprietary software > recently, I was asked to run `service foo restart`, and was surprised to > see: > foobar ~ # service foo restart > * service: service `foo' does not exist You saw this because "service" is really rc-service. At some point in the past, I was asked to add the "service" command to OpenRC, and all it is is a synonym for rc-service.
> Since `systemctl restart foo` works, I had a workaround anyway. > > Talking with Whubbs about it, I found that our service script only > supports OpenRC, via rc-service. I looked around, and from what I can > tell, most distros ship a service tool for all supported init systems. I.e., > Debian/Ubuntu: supports sysvinit and systemd via init-system-helpers > CentOS/Fedora: provides support for systemd via initscripts > OpenSUSE: has a working service binary for systemd (according to #suse) > > I'd like to propose moving `service` out of OpenRC and into a separate > package that OpenRC and systemd can both use. It's very possible that we > could simply package/use another distro's scripts (I haven't evaluated > that though). I would support this. "service" should be a command, separate from any service manager, that can be a wrapper for multiple service managers. It isn't something that the service managers have to care about, it would just be a convenience tool for users. I can start setting up for this as soon as OpenRC 0.33 by removing the service binary from OpenRC. Thanks, William
signature.asc
Description: Digital signature
