STATUS: RUNNING
BUILD: 1.6_M2_RC1: e4c23f7bcb79072ea6028fbdf8f3f0dc17a63371
ENVIRONMENT: Multiple environments
STEPS TO REPRODUCE: 
  
Prepare a core-image-minimal image with systemd support and launch it. 
     Refer to TC-549 in order how to build it.
Show status of a service
    # systemctl show syslog.socket
Stop a running service:
    # systemctl stop syslog.socket
Enable a service:
    # systemctl enable syslog.socket
Verify the service status:
    # systemctl is-enabled syslog.socket
Disable the service
    # systemctl disable syslog.socket
Verify the service status:
    # systemctl is-enabled syslog.socket

EXPECTED OUTCOME: 2. Information should be displayed for the service
3. The service is stopped
4. The service is enabled
5. It is displayed that the service appears to be enabled
6. The service is disabled
7. It is displayed that the service appears to be disabled

Actual outcome:

1. When running systemctl stop syslog.socket, the service is not stopped:

root@qemux86:~# systemctl stop syslog.socket
root@qemux86:~# ps | grep syslog
  100 root      2480 S    /sbin/syslogd -n -C

2. When running systemctl enable syslog.socket, following issue appear:

root@qemux86:~# systemctl enable syslog.socket
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).

3. When disabling the service, systemctl shows the syslog.socket as being static and not as disabled/enabled:

root@qemux86:~# systemctl disable syslog.socket
root@qemux86:~# systemctl is-enabled syslog.socket
static

Cheers,
Ionut C