SUSE Support

Here When You Need Us

Epipe errors seen in log files

This document (7003193) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 10


Epipe error messages are seen in log file.


Please refer to man 7 pipe:
If all file descriptors referring to the write end of a pipe have  been closed,  then  an attempt to read(2) from the pipe will see end-of-file (read(2) will return 0).  If all file descriptors referring to the read end  of  a  pipe have been closed, then a write(2) will cause a SIGPIPE signal to be generated for the calling process.  If the calling process is  ignoring this signal, then write(2) fails with the error EPIPE.  An application that uses pipe(2) and fork(2) should use suitable  close(2) calls  to  close  unnecessary  duplicate file descriptors; this ensures that end-of-file and SIGPIPE/EPIPE are delivered when appropriate.


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7003193
  • Creation Date: 01-May-2009
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.