Bug 723318 - [FEAT] Have systemctl automatically append the .service to the service name
Summary: [FEAT] Have systemctl automatically append the .service to the service name
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 18:26 UTC by Steve Dickson
Modified: 2011-07-20 01:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-19 21:16:20 UTC
Type: ---


Attachments (Terms of Use)

Description Steve Dickson 2011-07-19 18:26:33 UTC
Description of Feature Request:

To start a service one does 
    systemctl start foobar.service 

Since the '.service' is the static part of all service names it 
would be nice if the systemctl would just automatically append 
the '.service' when its not supplied. So the above command
would turn into:
   systemctl start foobar

Version-Release number of selected component (if applicable):
systemd-units-30-1.fc16.x86_64

Comment 1 Bill Nottingham 2011-07-19 18:38:06 UTC
Note that systemctl can start many types of units - service is only one of the types.

Comment 2 Steve Dickson 2011-07-19 19:58:32 UTC
(In reply to comment #1)
> Note that systemctl can start many types of units - service is only one of the
> types.

So for the systemctl [start|restart|enable]' commands that actually
start and stop services, the given service file does not have to end 
with '.service' ?

Comment 3 Bill Nottingham 2011-07-19 20:06:01 UTC
Trying to be a bit more clear - systemd operates on unit files; these unit files can come in different types, distinguished by file extension:

- service
- socket
- device
- mount
- automount
- swap
- target
- path
- timer

start, stop, eanble, etc. are valid actions for multiple unit types, not just services.

Comment 4 Steve Dickson 2011-07-19 21:16:20 UTC
(In reply to comment #3)
> Trying to be a bit more clear - systemd operates on unit files; these unit
> files can come in different types, distinguished by file extension:
> 
> - service
> - socket
> - device
> - mount
> - automount
> - swap
> - target
> - path
> - timer
> 
> start, stop, eanble, etc. are valid actions for multiple unit types, not just
> services.

Ok... Just trying to help make things a bit more streamline...
I'm just notice I'm doing a lot '.service' typing lately 
and I hoping try figure out a way around it...

Comment 5 Rahul Sundaram 2011-07-20 01:51:52 UTC
install bash-completion


Note You need to log in before you can comment on or make changes to this bug.