systemctl set-property implies --runtime for transient units

Submission type

• Bug report

systemd version the issue has been seen with

• systemd-235

Used distribution

• Fedora

In case of bug report: Expected behaviour you didn't see

• systemctl set-property user-0.slice CPUShares=2048 creates drop-in 50-CPUShares.conf in /etc/systemd/system/user-0.slice.d directory

In case of bug report: Unexpected behaviour you saw

Drop-in is created in /run/systemd/transient/user-0.slice.d

In case of bug report: Steps to reproduce the problem

1. log in as root
2. systemctl set-property user-0.slice CPUShares=2048
3. systemctl status user-0.slice

   Loaded: loaded (/run/systemd/transient/user-0.slice; transient; vendor preset: disabled)                                    
Transient: yes                                                 
  Drop-In: /run/systemd/transient/user-0.slice.d               
           └─50-CPUShares.conf                                 
   Active: active since Mon 2017-10-16 05:45:05 EDT; 1min 27s ago                                                              
    Tasks: 10 (limit: 10813)                                   
   Memory: 15.5M                                               
      CPU: 352ms                                               
   CGroup: /user.slice/user-0.slice                            
           ├─session-3.scope                                   
           │ ├─670 sshd: root [priv]                           
           │ ├─680 sshd: root@pts/0                            
           │ ├─880 bash -c cd ; bash -l                        
           │ ├─895 bash -l                                     
           │ ├─919 systemctl status user-0.slice               
           │ └─920 less                                        
           ├─session-5.scope                                   
           │ ├─779 sshd: root [priv]                           
           │ └─830 sshd: root                                  
           └─user@0.service                                    
             └─init.scope                                      
               ├─673 /usr/lib/systemd/systemd --user           
               └─675 (sd-pam)                        

Note that Drop-In references runtime config even though we didn't use --runtime option.

Reproduce the behavior with systemctl set-property user-0.slice CPUShares=2048 and inspect the resulting systemctl status output. Compare the reported /run/systemd/transient/user-0.slice.d drop-in with the expected persistent /etc/systemd/system/user-0.slice.d location; done means the behavior matches the intended handling when --runtime is omitted.