Description of problem:

If I start a service with "sudo service daemond start", it remains attached to my systemd:/user/ cgroup.

The service command should, in addition to clearing the environment

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

current rawhide.

How reproducible:

inherent

Steps to Reproduce:
1. start a server with 'sudo service httpd start'
2. note the pid of the running process
3. look at /proc/<pid/cgroup 
  
(Note that I'm just using httpd as an example here; httpd will probably really be started by and controlled natively by systemd once this all goes into production.)

Actual results:

1:name=systemd:/user/mattdm/1

Expected results:

Some other cgroup, corresponding to what you'd get if the service were started by sysvinit scripts at boot time.