Shell Programming and Scripting

Hi!
I need to pass a few (as much as possible) arguments to one "key", i.e.

./myscript.sh -i one -b 1.1.1.1 2.2.2.2 3.3.3.3 ... -u users

I need to supply one or many IP adresses as a parameters.. I've search in getopts capabilities, but didn't find something for me. One of possibilities I thought - is to quote all list of IP addresses and consider it one argument. But it need more user involving, and I don't want it. Maye some "while" loop can help here?
Thanks for advance

P.S.
Another question (in order not multiply threads). How can I show in web page running output of shell script? Perl/PHP tools? If you have links - please.

If the IP addresses are required, don't make them options (that would indicate they are optional, anyway). In other words, any non-option arguments are IP addresses.

I cannot come up with an alternative which is unambiguous if you don't want the user to quote the list of IP addresses. (You can avoid quoting by using a separator which is not whitespace, of course. Maybe separating the IP addresses with a colon would be acceptable.)

Threads are not a limited resource, and it's actually better to post different questions in different threads. Your question is not very specific, but if this is a CGI script, anything it prints will be visible in the web browser (provided it adheres to some minimal formatting standards). Read the CGI spec, it's really quite simple.

If it's not CGI, perhaps you just want to redirect the output to a text file which is in the document tree of your web server.

Code:

command >~/public_html/output.txt

... would make the output available at http://server/~you/output.txt depending of course on how your web server is configured (and the file probably needs to be chmod a+r).

Thanks, era!
I think it'll be OK, if user separate it by comma. Can you give an example of arguments parsing in this case? Simply to grab all the ip-list to $1 with "case" and then go on it with "foreach"?
Although this can cause another problem with input like "1.1.1.1, 2.2.2.2", where there's whitespace after the comma. But I think there need be some limits for users' input errors and their prevention..If they don't want it working, don't let them touch it.. )
Thanks for CGI, I'll look at it.

An obscure but fairly common technique is to temporarily tell the shell that the IFS (internal field separator) is the separator you want to use, then just use a particular form of set to perform regular argument splitting into $1, $2, $3, etc.

Code:

OLDIFS=$IFS
IFS=','
set -- $1
IFS=$OLDIFS

for ip in "$@"; do
  echo have $ip
done