From: Elizabeth Figura zfigura@codeweavers.com
Named pipes are now implemented entirely on the server side, and there is no code that warrants a separate FD type. --- server/named_pipe.c | 2 +- server/protocol.def | 1 - 2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/server/named_pipe.c b/server/named_pipe.c index f3404a33c3b..dd8c14b30a9 100644 --- a/server/named_pipe.c +++ b/server/named_pipe.c @@ -1016,7 +1016,7 @@ static void pipe_end_reselect_async( struct fd *fd, struct async_queue *queue )
static enum server_fd_type pipe_end_get_fd_type( struct fd *fd ) { - return FD_TYPE_PIPE; + return FD_TYPE_DEVICE; }
static void pipe_end_peek( struct pipe_end *pipe_end ) diff --git a/server/protocol.def b/server/protocol.def index 12eef14cc67..73c73dd1948 100644 --- a/server/protocol.def +++ b/server/protocol.def @@ -1502,7 +1502,6 @@ enum server_fd_type FD_TYPE_DIR, /* directory */ FD_TYPE_SOCKET, /* socket */ FD_TYPE_SERIAL, /* serial port */ - FD_TYPE_PIPE, /* named pipe */ FD_TYPE_MAILSLOT, /* mailslot */ FD_TYPE_CHAR, /* unspecified char device */ FD_TYPE_DEVICE, /* Windows device file */