On Thu, 2010-03-25 at 15:27 -0700, [email protected] wrote: > I understand that the app is mistaken in dropping the socket. But I'm > getting some pressure to modify upstart to close the socket when this > happens so we're less vulnerable to errors like this. Are there good > reasons to keep the socket open in this case? (We're on 0.3.8 thanks > to our build system having a really old autoconf, but the latest code > seems the same: errors from sendmsg() are noted but not otherwise > acted on.) > What latest code are you looking at?
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. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
