From: Zilvinas Valinskas <zilvinas@gemtek.lt>
To: linux-kernel@vger.kernel.org
Subject: sendfile(2) behaviour has changed ?
Date: Wed, 16 Oct 2002 10:49:08 +0200 [thread overview]
Message-ID: <20021016084908.GA770@gemtek.lt> (raw)
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
This sample code copies a file using sendfile(2) call works just fine on
2.2.x and 2.4.x kernels. On 2.5.x kernels (not sure starting which
version) it stopped working. Program terminates with EINVAL error.
$ ./sendfile
sendfile: Invalid argument
Is this expected behaviour ? that sendfile(2) on 2.5.4x linux kernel requires
socket as an output fd paramter ?
Was it ever legal to copy file(s) on filesystem using sendfile(2) ?
(which was kindda nice feature ... )
[-- Attachment #2: sendfile.c --]
[-- Type: text/x-csrc, Size: 642 bytes --]
#include <sys/sendfile.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
int main()
{
int fd_in = 0;
int fd_out = 0;
struct stat stat_buf;
off_t offset = 0;
ssize_t count = 0;
if ((fd_in=open("sendfile.c",O_RDONLY))<0)
{
perror("open");
exit(1);
}
if ((fd_out=open("sendfile.out",O_CREAT|O_TRUNC|O_WRONLY,S_IRWXU))<0)
{
perror("open");
exit(1);
}
if (fstat(fd_in,&stat_buf)) {
perror("fstat");
}
count = sendfile(fd_out,fd_in,&offset,stat_buf.st_size);
if (count < 0)
perror("sendfile");
if (close(fd_in) < 0)
perror("close");
if (close(fd_out) < 0)
perror("close");
return 0;
}
next reply other threads:[~2002-10-16 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 8:49 Zilvinas Valinskas [this message]
2002-10-16 9:10 ` sendfile(2) behaviour has changed ? Matti Aarnio
2002-10-16 9:59 ` David S. Miller
2002-10-16 10:25 ` bert hubert
2002-10-17 20:51 ` James Antill
2002-10-17 22:41 ` David S. Miller
2002-10-17 23:23 ` James Antill
-- strict thread matches above, loose matches on Subject: below --
2002-10-20 9:50 sendfile(2) behaviour has changed? Dan Maas
2002-10-24 22:37 ` Jamie Lokier
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=20021016084908.GA770@gemtek.lt \
--to=zilvinas@gemtek.lt \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.