Attachment 2924 Details for Bug 3957 – AIX changes for Xtranssock.c

[patch] AIX changes for Xtranssock.c

Xtranssock.c.patch (text/plain), 1.48 KB, created by Dan McNichol on 2005-08-18 21:06:39 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Dan McNichol

Created: 2005-08-18 21:06:39 UTC

Size: 1.48 KB

patch

obsolete

>*** Xtranssock.c.orig   Sun Jul  3 02:01:01 2005
>--- Xtranssock.c        Tue Aug  2 16:00:12 2005
>***************
>*** 2225,2252 ****
>      /*
>       * If this is the server side, then once the socket is closed,
>       * it must be unlinked to completely close it
>       */
> 
>      struct sockaddr_un        *sockname = (struct sockaddr_un *) ciptr->addr;
>-     char      path[200]; /* > sizeof sun_path +1 */
>      int ret;
> 
>      PRMSG (2,"SocketUNIXClose(%p,%d)\n", ciptr, ciptr->fd, 0);
> 
>      ret = close(ciptr->fd);
> 
>      if (ciptr->flags
>         && sockname
>         && sockname->sun_family == AF_UNIX
>         && sockname->sun_path[0])
>      {
>-       strncpy (path, sockname->sun_path,
>-               ciptr->addrlen - sizeof (sockname->sun_family));
>        if (!(ciptr->flags & TRANS_NOUNLINK))
>!               unlink (path);
>      }
> 
>      return ret;
>  }
> 
>  static int
>--- 2225,2249 ----
>      /*
>       * If this is the server side, then once the socket is closed,
>       * it must be unlinked to completely close it
>       */
> 
>      struct sockaddr_un        *sockname = (struct sockaddr_un *) ciptr->addr;
>      int ret;
> 
>      PRMSG (2,"SocketUNIXClose(%p,%d)\n", ciptr, ciptr->fd, 0);
> 
>      ret = close(ciptr->fd);
> 
>      if (ciptr->flags
>         && sockname
>         && sockname->sun_family == AF_UNIX
>         && sockname->sun_path[0])
>      {
>        if (!(ciptr->flags & TRANS_NOUNLINK))
>!               unlink (sockname->sun_path);
>      }
> 
>      return ret;
>  }
>
>  static int

Actions: View | Splinter Review

Attachments on bug 3957: 2924 | 2925

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.