From owner-freebsd-bugs Thu Aug 7 05:30:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA05192 for bugs-outgoing; Thu, 7 Aug 1997 05:30:04 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA05182; Thu, 7 Aug 1997 05:30:02 -0700 (PDT) Date: Thu, 7 Aug 1997 05:30:02 -0700 (PDT) Message-Id: <199708071230.FAA05182@hub.freebsd.org> To: freebsd-bugs Cc: From: David Greenman Subject: Re: kern/4243: file locking doesn't work for pipe Reply-To: David Greenman Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/4243; it has been noted by GNATS. From: David Greenman To: tetsuya@secom-sis.co.jp Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/4243: file locking doesn't work for pipe Date: Thu, 07 Aug 1997 05:22:17 -0700 >In flock() in /sys/kern/kern_descrip.c, the following statement: > > f (fp->f_type != DTYPE_VNODE) > return (EOPNOTSUPP); > >rejects the file descriptor if fp->f_type == DTYPE_PIPE. >F_SETLK and F_GETLK of fcntl() have also the similar statements. > >"Program rewriting map" (RewriteMap mapname prg:filename) of >the URL rewriting module (mod_rewrite) of the Apache HTTP server >uses file locking for pipe, so FreeBSD users cannot use the fine >feature of "program rewriting map". Hmmm. Maybe I'm missing something obvious, but I can't think of a reason why one would want to do file locking on a pipe (which is not a shared resource). This sounds like a bug in Apache to me... -DG David Greenman Core-team/Principal Architect, The FreeBSD Project