(OK) init: Service exec 1 (/system/bin/logwrapper) does not have a SELinux domain defined.

--------------------------------------------------------------------
init: Service exec 1 (/system/bin/logwrapper) does not have a SELinux domain defined.
--------------------------------------------------------------------

http://blog.csdn.net/xusiwei1236/article/details/41577231

--------------------------------------------------------------------

Debugging notes
------------------------
By default, programs executed by init will drop stdout and stderr into /dev/null. To help with debugging, you can execute your program via the Andoird program logwrapper. This will redirect stdout/stderr into the Android logging system (accessed via logcat).

For example:

service akmd /system/bin/logwrapper /sbin/akmd

--------------------------------------------------------------------

https://sourceforge.net/p/android-x86/system_core/ci/9464e5a58da50f6cc3503020b38181150cfd01c4/log/?path=/init/init.c

--------------------------------------------------------------------

Add support for socket security context specification.

Add an optional argument to the socket option for specifying a SELinux security context for the socket. Normally the socket security context is automatically computed from the service security context or set using the seclabel option, but this facility allows dealing with two scenarios that cannot be addressed using the existing mechanisms:

1) Use of logwrapper to wrap a service.

In this case, init cannot determine the service security context as it does not directly execute it and we do not want logwrapper to run in the same domain as the service.

2) Situations where a service has multiple sockets and we want to label them distinctly.

--------------------------------------------------------------------