Path: utzoo!attcan!uunet!mcsun!hp4nl!phigate!ehviea!leo
From: leo@ehviea.ine.philips.nl (Leo de Wit)
Newsgroups: comp.unix.questions
Subject: Re: SEX!  or, how do I mail to a lot of unix users?
Message-ID: <804@ehviea.ine.philips.nl>
Date: 5 Jun 90 16:33:03 GMT
References: <900531083002.30e0d06c@Csa2.LBL.Gov> <JASON.90May31163242@aelle.cs.odu.edu> <1990May31.230138.14896@iwarp.intel.com>
Reply-To: leo@ehviea.UUCP (Leo de Wit)
Organization: Philips I&E Eindhoven
Lines: 42

In article <1990May31.230138.14896@iwarp.intel.com> merlyn@iwarp.intel.com (Randal Schwartz) writes:
|In article <JASON.90May31163242@aelle.cs.odu.edu>, jason@cs (Jason C Austin) writes:
|| #!/bin/sh
|| 
|| users=`cat user-list`

1 fork, 1 exec.

|| 
|| for user in $users
||  do
||   echo "Mailing $user"
||   mail $user < message
||  done
|

2 forks & 2 execs for each user.

|
|Too many processes.  If you want progress reporting, say:
|
|while read user
|do
|	echo "Mailing $user"
|	mail $user <message
|done <user-list
|

1 fork for the redirected while, 2 forks & 2 execs for each user.

Number of processes is the same (but you save an exec).
Alternative:

set -x     # Let the shell do the progress report.
for user in `cat user-list`; do mail $user <message; done

(1 fork & 1 exec for cat, 1 fork & 1 exec for each user).

Of course, for builtin echo's, not-forked redirected while loops the
situation differs.

    Leo.