Upstart spins forever when sender fails to call recv()

[Scott James Remnant]

On Fri, 2010-03-26 at 07:43 -0700, upstart at eehouse.org wrote:

> > Upstart hasn't shipped a "libupstart" for the best part of two years,
> > that code is long dead and buried.
> > 
> > All Upstart versions since 0.5.0 (0.6.5 is current) use D-Bus for
> > communication.
> 
> 0.5.1 still calls sendmsg() in nih_io_message_send(), and ignores all
> errors beyond raising them.
> 
nih_io_message_send() does not get called anywhere - it's dead code.

> Given that we're stuck with 0.3.8 for the time being, and so with its
> socket-based IPC, would you recommend against closing sockets in cases
> like this where the client is not listening?  Are there any cases
> where socket errors should result in closing the socket and giving up
> on whatever reply or message was meant for it?
> 
I do not provide support for 0.3.x -- I recommend that you update to
0.6.5

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20100326/14c9f8b2/attachment.pgp