From: Frank de Lange <bluez-f@unternet.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sdpd in polling loop on disconnect
Date: Mon, 19 Feb 2007 22:36:35 +0100 [thread overview]
Message-ID: <45DA1863.1000103@unternet.org> (raw)
In-Reply-To: <45DA144F.1090506@unternet.org>
Frank de Lange wrote:
> Marcel Holtmann wrote:
>>> Attached: patch for sdpd (adds G_IO_HUP|G_IO_ERR to watched conditions
>>> on g_io_channels)
>> thanks for the patch, but that should be already fixed in the CVS. Johan
>> found this during the UPF testing last week.
>
> Even better. Did he also check the other watchers for similar problems?
> As said there are several of them which only look for G_IO_IN events.
>
> Cheers//Frank
>
Replying to my own message here... I checked current CVS for the above
and found a few remaining occurrences of listening watchers which don't
care for HUP:
utils/daemon/echo.c:176
utils/hcid/main.c:782
utils/input/server.c:233
utils/test/hciemu.c:1331
utils/transfer/server.c:108
Are these accounted for as being 'safe'?
Cheers//Frank
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-02-19 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 0:31 [Bluez-devel] sdpd in polling loop on disconnect Frank de Lange
2007-02-16 2:00 ` Marcel Holtmann
2007-02-19 20:00 ` Frank de Lange
2007-02-19 20:33 ` Marcel Holtmann
2007-02-19 21:19 ` Frank de Lange
2007-02-19 21:28 ` Johan Hedberg
2007-02-19 21:31 ` Marcel Holtmann
2007-02-19 21:36 ` Frank de Lange [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45DA1863.1000103@unternet.org \
--to=bluez-f@unternet.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox