From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: Ardhan Madras <nightdecoder@gmail.com>,
linux-c-programming@vger.kernel.org
Subject: Re: Help on pipe
Date: Fri, 10 Jul 2009 09:06:27 +0200 [thread overview]
Message-ID: <op.uwubc1lg7p4s8u@amdc030.digital.local> (raw)
In-Reply-To: <34e1241d0907092322h5aea016cj437168a43ebfe50e@mail.gmail.com>
On Fri, 10 Jul 2009 08:22:54 +0200, Ardhan Madras <nightdecoder@gmail.com>
wrote:
> #include <sys/types.h>
> #include <sys/wait.h>
> #include <unistd.h>
> #include <stdio.h>
> #include <string.h>
>
> int main(void)
> {
> pid_t pid;
> int fds[2], ret;
> const char *sort = "/usr/bin/sort";
"static const char sort[]" would be better IMO.
> char *argv[2] = { "sort", NULL };
"static const char *argv[]" is definitly better here and does not produce
warnings. Your code discards "const" from pointer (a string literal).
> ret = pipe(fds);
> if (ret == -1) {
> perror("pipe");
> return -1;
> }
> pid = fork();
> if (pid == -1) {
> perror("fork");
> return -1;
> }
Personally I preffer something like:
switch (fork()) {
case -1: /* error */ break;
case 0: /* child */ break;
default: /* parent */
}
but suit yourself.
> if (pid == 0) {
> int ret;
No need to define this variable here. You already have such variable.
>
> close(fds[1]);
> dup2(fds[0], STDIN_FILENO);
>
> ret = execve(sort, argv, NULL);
> if (ret == -1) {
> perror("execve");
> }
> close(fds[0]);
> _exit(0);
No need to close(), and _exit(0) should be _exit(1) (or -1 if you will)
since the chiled finished with error.
> }
> else {
> FILE *stream;
>
> close(fds[0]);
> stream = fdopen(fds[1], "w");
> if (!stream) {
> perror("fdopen");
> return -1;
> }
> fprintf(stream, "this\n");
> fprintf(stream, "means\n");
> fprintf(stream, "war\n");
> fflush(stream);
And here, replace fflush() with fclose(). It seems, data is buffered on
kernel level, not only libc level and fflush() cannot handle that.
> waitpid(pid, &ret, 0);
> close(fds[1]);
No need to close.
> }
> return 0;
> }
--
Best regards, _ _
.o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał "mina86" Nazarewicz (o o)
ooo +-<m.nazarewicz@samsung.com>-<mina86@jabber.org>-ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-10 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 6:22 Help on pipe Ardhan Madras
2009-07-10 7:06 ` Michał Nazarewicz [this message]
2009-07-10 7:34 ` Ardhan Madras
2009-07-10 17:40 ` Glynn Clements
2009-07-11 3:41 ` David Lee
2009-07-13 6:45 ` Michał Nazarewicz
2009-07-10 7:27 ` David Lee
-- strict thread matches above, loose matches on Subject: below --
2009-07-10 18:21 Ardhan Madras
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=op.uwubc1lg7p4s8u@amdc030.digital.local \
--to=m.nazarewicz@samsung.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=nightdecoder@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).