2012-10-10 15:59:29

by Marti Raudsepp

Subject: [PATCH] systemd: prevent duplicate logging messages in journal

By default, both stdout and syslog messages go to the systemd journal,
which results in duplicate messages being logged.
---
src/bluetooth.service.in | 1 +
1 file changed, 1 insertion(+)

diff --git a/src/bluetooth.service.in b/src/bluetooth.service.in
index 2a576a3..a8442a9 100644
--- a/src/bluetooth.service.in
+++ b/src/bluetooth.service.in
@@ -5,6 +5,7 @@ Description=Bluetooth service
Type=dbus
BusName=org.bluez
ExecStart=@prefix@/sbin/bluetoothd -n
+StandardOutput=null

[Install]
WantedBy=bluetooth.target
--
1.7.12.2

2012-10-25 23:30:06

by Marcel Holtmann

Subject: Re: [PATCH] systemd: prevent duplicate logging messages in journal

Hi Marti,

> By default, both stdout and syslog messages go to the systemd journal,
> which results in duplicate messages being logged.
> ---
> src/bluetooth.service.in | 1 +
> 1 file changed, 1 insertion(+)

patch has been applied.

Regards

Marcel

2012-10-25 02:12:36

by Vinicius Costa Gomes

Subject: Re: [PATCH] systemd: prevent duplicate logging messages in journal

Hi Marti,

On 18:59 Wed 10 Oct, Marti Raudsepp wrote:
> By default, both stdout and syslog messages go to the systemd journal,
> which results in duplicate messages being logged.
> ---

Patch looks good.

Ack.

On a side note: seems that connman and ofono have the same problem, would you
be interested on sending the respective fixes?

> src/bluetooth.service.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/src/bluetooth.service.in b/src/bluetooth.service.in
> index 2a576a3..a8442a9 100644
> --- a/src/bluetooth.service.in
> +++ b/src/bluetooth.service.in
> @@ -5,6 +5,7 @@ Description=Bluetooth service
> Type=dbus
> BusName=org.bluez
> ExecStart=@prefix@/sbin/bluetoothd -n
> +StandardOutput=null
>
> [Install]
> WantedBy=bluetooth.target
> --
> 1.7.12.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html


Cheers,
--
Vinicius