(re-posting in rhel7 branch)

Also let me explain why I like service fooserverd disable|enable:

Workflow is like this:

1) yum -y install foo-server

2) service fooserverd start
3) service fooserverd status # everything seems good, ready to enable
4) service fooserverd enable  
5) service fooserverd status # double check enabled

You see on all lines 2-4) the only thing changing is the last argument,
arrow up (in history), then delete some chars and then new command, 
this goes very fast and easy.

Using: 

systemctl start|enable|status fooserverd

you have to move over the last word argument (foodserverd) 
several times, this is slow and error prune.

Power to the user/admin is more important than some LSB thingie, agree?

Terje, I got your point, but on the other hand, systemctl provides much more than service command and we would like to encourage users to switch from service to systemctl. If you look back, you had to use chkconfig to enable/disable services and service to start/stop/restart them...Now you have one command that does all of that and much more.

(re-post)

If systemd was user friendly in the first place this would not be a problem.

Why create a new command which is 9 letters long? 

And with no fast tab completion possible and has arguments in wrong order to top it?

Think if 'ls' command was renamed to listmyfiles and you had to have options after arguments, like this:

$ listmyfiles /etc -lrtc

Why can't the guys  making this stuff care a bit about the users?

Forcing sysadmins to use awkward systemctl command seems strange at best.

Ideal would be to introduce a short command, e.g. srv with correct
order of arguments and a small subset of needed commands and a 
nice manual page to follow.

$ srv fooserverd stop|start|restart|status|enable|disable

Can't be that hard to implement?

Correct me if I'm wrong but pre-systemd 'service xyz enable' only worked if the initscript implemented the action itself i.e. it wasn't a feature of service.

At least that's how service works on rhel6:
# service postfix enable
Usage: /etc/init.d/postfix {start|stop|restart|reload|abort|flush|check|status|condrestart}

Equivalent functionality for rhel7 is to implement the enable/disable actions via the legacy actions[1]. Or calling chkconfig as usual - it works on rhel7 too.

[1] /usr/libexec/initscripts/legacy-actions/

That's correct.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.