Bug 906824

Description of problem:

The general idea goes something like this.. 

Admin runs "systemctl edit my.service"

1. systemd reads the $EDITOR variable from shell if undefined falls back to use vi(m) which is posix standard ( I think ed is as well but hey who remembers and used ed ;) )


three use cases I can think of when admin wants edit units 

1. An admin wants to create new unit file. ( empty template based on ending kind a must have for timer units for users )
2. An admin wants to make minor changes to unit file ( .include )
3. An admin wants to make major changes to unit file ( copy unit )
 
1. a new file is opened based on a unit template like would open the file /etc/systemd/system/my.service with .service template 

[Unit]
Description=
Before=
After=

[Service]
Type=
PIDFile=/var/run/
ExecStarPre=
ExecStart=
ExecReload=
ExecStop=
...

[Install]
WantedBy=multi-user.target



2. an file is opened in /etc/systemd/system/my.service containing only .include reference and [Service]


3. my.service is copied to /etc/systemd/system/ directory

4. once file is saved systemd is reload to pick up the changes.

systemctl edit my.service covers both first and second use cases as in if file does not exist (1) then create an new one based on template. If file exist open it with .include file 

Usecase 3 should be seperated command something like "systemctl edit my.service --full" to copy/edit an entire unit. 

I do believe we need something like 1 for timer units to provide similar if not easier cron experience as in user can just run systemctl edit my.timer and it provides him with a timer unit skeleton which he essentially just has to specify the path to what he's going to execute and the time he's going to do it. 
 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: