Send plymouth mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.freedesktop.org/mailman/listinfo/plymouth
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of plymouth digest..."


Today's Topics:

   1. Re: [PATCH] fix old socket name after 9de731ed and 3ec007a4
      (Ray Strode)


----------------------------------------------------------------------

Message: 1
Date: Fri, 19 Nov 2010 10:35:55 -0500
From: Ray Strode <[email protected]>
Subject: Re: [PATCH] fix old socket name after 9de731ed and 3ec007a4
To: Andrey Borzenkov <[email protected]>
Cc: [email protected]
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8

Hi,

On Thu, Nov 18, 2010 at 1:35 PM, Andrey Borzenkov <[email protected]> wrote:
> Commit 9de731ed29db4670c1641aedd945c56fd1a3feed caused
> plymouth to lose leading '\0' on old abstract socket
> making it incompatible with older server. As result new
> client (after update) can no more communicate with old
> running server (or older server as part of initrd).
>
> Restore proper behaviour of having leading '\0' for both
> abstract sockets, trimmed and non-trimmed.
>
> Commit 3ec007a4820e53aed6713620173bd997957754ec did not
> check for success with old socket path and failed
> always. Properly check for success and proceed.

Thanks, these are commited now:

http://cgit.freedesktop.org/plymouth/commit/?id=a4c7cbafd3b448b24c50181132be6180ebed9621
http://cgit.freedesktop.org/plymouth/commit/?id=d29722b34a49cb432bd2ea83206447223667198c

--Ray


------------------------------

_______________________________________________
plymouth mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/plymouth


End of plymouth Digest, Vol 25, Issue 5
***************************************

Reply via email to