public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org, richard@bouska.cz
Subject: Re: NFS mountned  directory  and apache2 (2.5.47)
Date: Fri, 15 Nov 2002 19:19:06 +0100	[thread overview]
Message-ID: <79A23782BB8@vcnet.vc.cvut.cz> (raw)

On 15 Nov 02 at 19:10, Trond Myklebust wrote:

>      > Hello In 2.45.47 and 2.5.46 (at least) did not try any other am
>      > I not able to serve files bigger than 255 bytes by apache2 from
>      > nfs mounted directory. The local files are served correctly.
> 
> Looks like whoever it was that changed the 'sendfile' API forgot to
> update NFS. Try the following patch.

It does not change anything on the brokeness of apache2 (or maybe
glibc). It must be able to revert to read/write loop if sendfile fails
with EINVAL. There is no guarantee that existing sendfile() API means
that you can use it with all filesystems.
                                            Best regards,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz
                                                

             reply	other threads:[~2002-11-15 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 18:19 Petr Vandrovec [this message]
2002-11-15 20:16 ` NFS mountned directory and apache2 (2.5.47) Trond Myklebust
2002-11-15 20:26   ` Christoph Hellwig
2002-11-15 20:53     ` Trond Myklebust
2002-11-16  4:44       ` Christoph Hellwig
2002-11-17 20:18         ` Trond Myklebust
2002-11-15 21:10     ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2002-11-15 10:25 Richard Bouska
2002-11-15 18:10 ` Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=79A23782BB8@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@bouska.cz \
    --cc=trond.myklebust@fys.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox