From: Support (support@XIATECS.NET)
Date: Tue Feb 10 2004 - 14:21:19 EST
This happens when there is a large write to the named pipe, and the read
request is not able to keep up with the write request. I'm not 100% sure
on how it works, but I think the write process to the pipe will be
blocked until the read request has time to catch up. The following entry
is in the /usr/include/sys/limits.h file:
#define PIPE_BUF 32768 /* max number of bytes that is
guaranteed to be atomic when
writing
to a pipe, >= 512 */
Hope this helps,
_________________________________
Sukhjeet Singh
Senior Technology Consultant
IBM Certified Specialist - AIX
Xiatecs Systems Consultants Inc.
Tel: +1.514.668.0838
www.xiatecs.net - ssingh@xiatecs.net
_________________________________
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
Holger.VanKoll@SWISSCOM.COM
Sent: Tuesday, February 10, 2004 11:11 AM
To: aix-l@Princeton.EDU
Subject: named pipe
Hello,
what does it mean if a named pipe has a filesize >0 ?
prw-r--r-- 1 oracle dba 32768 Feb 10 14:39 /tmp/imp_pipe
Regards,
Holger
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:35 EDT