Bug 32719 – rfcomm (net-wireless/bluez-utils) should flush stdout

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Sybren Stüvel 2003-11-04 08:40:14 UTC]

rfcomm (part of net-wireless/bluez-utils) should flush stdout when a new (incoming and/or outgoing) connection has been made. With this patch, scripts can use rfcomm to connect via bluetooth and fork() the process in order to start using the connection (ie. by running pppd over it).

[Comment 1 Sybren Stüvel 2003-11-04 08:41:56 UTC]

Created attachment 20256 [details, diff]
Patch for the bluez-utils-2.3.ebuild ebuild to use my bluez-utils-2.3-rfcomm.patch patch

Patch for the bluez-utils-2.3.ebuild ebuild to use my
bluez-utils-2.3-rfcomm.patch patch - will be attached after this one.

[Comment 2 Sybren Stüvel 2003-11-04 08:47:20 UTC]

Created attachment 20257 [details, diff]
Patches rfcomm to flush stdout

Patches rfcomm to flush stdout when a connection is made. This can be tested
like this:

rfcomm connect /dev/rfcomm0  00:11:22:33:44:55 2 | cat

Without my patch, you will see the output when the connection is closed and
rfcomm quits. With my patch, the output 'Connected /dev/rfcomm0 to
00:11:22:33:44:55 on channel 2' will be shown immediately upon connection,
allowing other scripts to react on the connection.

[Comment 3 Sybren Stüvel 2003-11-04 08:53:02 UTC]

PS: This is a complete, tested solution. At least on my box ;-)

[Comment 4 Alastair Tse (RETIRED) 2003-11-05 00:32:21 UTC]

sounds like a pretty harmless patch, i'll consider it for -r1. in the meantime,
have you posted this patch to the bluez developers?

[Comment 5 Alastair Tse (RETIRED) 2003-11-22 13:37:52 UTC]

i've added this to bluez-utils-2.3-r1. i didn't version bump it because it probably doesn't affect many users to force them to re-emerge.

[Comment 6 Sybren Stüvel 2003-11-23 08:01:30 UTC]

Sounds reasonable! Thanx for adding it to Gentoo - it's my first piece of code that was added to something Open Source that is so well known ;-)