Yedidyah Bar-David wrote:
On Tue, Oct 19, 2004 at 06:21:47AM +0200, [EMAIL PROTECTED] wrote:OK, right. Not necessarily multiple times but still each line is taken as a separate
That's wrong. If /tmp/tmp-sms contains multiple lines then sendsms
would be invoked separatly for each one of them.
Where did you get this from? xargs(1): " --max-chars=max-chars, -s max-chars Use at most max-chars characters per command line, including the command and initial arguments and the terminating nulls at the ends of the argument strings. The default is as large as possi- ble, up to 20k characters." As I said in a previous post, this isn't accurate - on Linux the max is more than that (around 128k). There are unices where the max is 20k, though.
command line argument, where sendsms (according to the replies so far, I haven't
looked at it) expects the entire message in a single command line argument.
Well, that's a matter of typing convenience, it's still an unnecesarily extra process in the
Beside that, when you use xargs to read a file then "cat" is redundand, you can just do:
xargs sendsms < /tmp/tmp-sms
This was mentioned a few months ago, and someone (was it Nadav Har`el?) said, and I agreed, that doing cat file | cmd1 | cmd2 | ... | cmdn is more convenient, because if cmd1 is long, and you want to prepend something before it, it's more work: you have to delete the '< file', go back, insert 'cmd0 < file', whereas with 'cat' you only add your '| cmd0' after the 'cat file |'.
pipe.
But we get each other's drift.
You are right - multiple lines will result in multiple command line arguments, not necessarily(but my previous point still holds - multiple lines will cause multiple
invocations of sendsms)
It still doesn't :-) (sorry, I had to).
multiple invocations.
--Amos
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
