Chris Adams (cmadams(a)hiwaay.net) said:
> > This is a very big change. chkconfig has worked for a long,
long time. Its
> > elegance and simplicity is one of the nice administrative features of Red
> > Hat based distributes. People like it.
> Yes, and they should continue to use it -- for sysv scripts.
I thought the last big discussion resulted in agreement that chkconfig
and service should continue to work for all services. Is that not the
service can, because it's pretty much a 1:1 mapping. (It's currently fixed
in git; it's telling you it's using systemctl while doing the appropriate
chkconfig is different, because it's not a 1:1 mapping, and there are
different semantics involved. I'd like to have it working so that the
automated uses in scripts/frameworks work (checking whether a service is
enabled, for example), with the realization that everything it's used for
isn't going to be supported.