>> >> I think man page should mention about this usage. > >Hmm, but it does - you even quoted the EINVAL return documentation >yourself. The description mentions that it dupes between the pipes >referred to by fd_in and fd_out. Not sure how much else we can do there? I meant it should explicitly describe how to use that example. ;) > >> >> Hi jens, >> >> >> >> Yes, I guessed you probably should run it like that. And it does produce >> >> the expected output on stdout. However, the command then blocks, and if >> >> one types control-C, the output_file is empty. How should this program be >> >> terminated so that something does end up in the output_file? >> > >> >See ktee.c from the splice sample repo, it works correctly: >> > >> >axboe@carl:~/git/splice> echo hello | ./ktee outfile | cat >> >hello >> >axboe@carl:~/git/splice> cat outfile >> >hello >> > >> >I don't have the tee(2) man page here so can't verify, but try and >> >compare them! >> > >> >> I have the same problem here with what Michael mentioned. >> But my output file is *not* empty. Shown below: >> >> $ echo hello | ./tee fooo.txt | cat >> hello >> <=== here blocked, type ctrl+c, exit >> $ cat fooo.txt >> hello >> >> My kernel version is 2.6.21-1.3194.fc7. > >I don't know what 'tee' is - is it the one from the man page, or the one >from my splice tools? My bad. The file "./tee" is just the output executable of the given example in tee(2). Thanks! - To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
