On Mon, Feb 19, 2007 at 01:28:17PM -0800, Christopher Layne wrote:
> Absolutely. I don't disagree with this. The issue is the magnitude.
> The opteron box has 4gigs of ram, scsi 320 disks, and is running water cooled
> at 2.8 ghz. Nothing *normal* can explain such a reason why a Celeron-D can
> for
On Mon, Feb 19, 2007 at 01:04:38PM -0800, Shankar Unni wrote:
> Christopher Layne wrote:
>
> >$ uname -a; uptime; time echo 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
> >18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
> >43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
Christopher Layne wrote:
$ uname -a; uptime; time echo 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
75 76 77 78 79 80 81 82
Christopher Layne wrote:
On Mon, Feb 19, 2007 at 05:34:31PM +0100, Corinna Vinschen wrote:
...or `xargs -n 1'
Which btw is obnoxiously slow on Cygwin for some weird-unknown
reason.
Hm. I thought Cygwin always popped up a message explaining why it
was being obnoxiously slow. Must be a bug.
On Mon, Feb 19, 2007 at 05:34:31PM +0100, Corinna Vinschen wrote:
> > >maybe I'm being dense, but xargs does not seem to do what
> > >it should:
> >
> > xargs only calls the command (echo in this case) once, with
> > all the given arguments. (It will call it more than once
> > only if calling it
On Mon, Feb 19, 2007 at 05:34:31PM +0100, Corinna Vinschen wrote:
> > If you want a command run once for each item in a list of
> > things, use a for loop:
>
> ...or `xargs -n 1'
>
>
> Corinna
Yeah, unfortunately don't try to do too much with that or you'll be
waiting for a while.
$ uname -a;
* Markus Hoenicka [2007.02.19 10:45]:
> $ echo test1 test2|xargs -t
> /bin/echo test1 test2
> test1 test2
>
> I'd expect the output to read:
>
> /bin/echo test1
> test1
> /bin/echo test2
> test2
Your assumption about what xargs does is
incorrect. It does not call the command once for
each argume
Aaron Brown <[EMAIL PROTECTED]> was heard to say:
> xargs only calls the command (echo in this case) once, with
> all the given arguments. (It will call it more than once
> only if calling it once would be a too-long command line.)
>
Ah, I see. After reading the man page again, the "-n" option w
On Feb 19 11:23, Aaron Brown wrote:
> Markus Hoenicka wrote:
>
> >maybe I'm being dense, but xargs does not seem to do what
> >it should:
>
> xargs only calls the command (echo in this case) once, with
> all the given arguments. (It will call it more than once
> only if calling it once would be
Markus Hoenicka wrote:
> maybe I'm being dense, but xargs does not seem to do what it should:
>
> $ echo test1 test2|xargs -t
> /bin/echo test1 test2
> test1 test2
>
> I'd expect the output to read:
>
> /bin/echo test1
> test1
> /bin/echo test2
> test2
>
> What am I doing wrong?
Your expectation
Markus Hoenicka wrote:
maybe I'm being dense, but xargs does not seem to do what
it should:
xargs only calls the command (echo in this case) once, with
all the given arguments. (It will call it more than once
only if calling it once would be a too-long command line.)
If you want a command ru
Hi all,
maybe I'm being dense, but xargs does not seem to do what it should:
$ echo test1 test2|xargs -t
/bin/echo test1 test2
test1 test2
I'd expect the output to read:
/bin/echo test1
test1
/bin/echo test2
test2
What am I doing wrong?
regards,
Markus
--
Markus Hoenicka
[EMAIL PROTECTED]
(
12 matches
Mail list logo
