| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the bluez5 init script to resolve an issue where the status
subcommand would exit without printing any message if bluez was not
running. The early exit was caused by the fact that the init script has
"set -e". When "pidof ${DAEMON} >/dev/null" is executed, the script
terminates immediately if bluez isn't running because pidof returns a
non-zero result. The fixed version does not suffer from this issue and
makes use of the "status" function from the functions library.
(From OE-Core rev: f6e03a43ee71c406fa8e68309624efd5384f437a)
Signed-off-by: David Frey <dpfrey@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix booting messages wrapped over two different lines:
Starting bluetooth
bluetoothd
Stopping bluetooth
/usr/libexec/bluetooth/bluetoothd
Also reworked whitespace (removed some empty lines).
(From OE-Core rev: 62f1122ef166eba56441d669c6b3b3fe5f367418)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
Within the sysvinit script the path to bluetoothd is wrong. Because of this
the init scripts silently terminates without any message
(From OE-Core rev: 63cde9b8101ed39376529f3205d32729341d5802)
Signed-off-by: Christian Ege <k4230r6@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
This is from Shrikant Bobade <Shrikant_Bobade@mentor.com>.
(From OE-Core rev: f4c16f53af27ad459e77ae7f43e7bf1bad70645a)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
