Courier User writes: > Here is a small subset of the group of tests that I performed on my > freebsd 4.0 system before posting my previous message:
> 1% echo "echo foo" >/tmp/xxx > 2% /usr/bin/env - /bin/sh -c ". /tmp/xxx; echo bar &" > bar > 3% /usr/bin/env - /bin/sh -c ". /tmp/xxx; echo bar" > foo > bar > You may not get these same results on your own system, but I > consistently get them on mine. > > As you can see, this is not due to "guesses". Your claim that the -c or the -a options are not portable was certainly a guess. This looks like an internal sh bug. This bug is fixed in FreeBSD 4.5. bash-2.05$ uname -a FreeBSD usf-cf-x86-freebsd-1.cf.sourceforge.net 4.5-STABLE FreeBSD 4.5-STABLE #5: Tue Apr 30 11:22:09 PDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 bash-2.05$ echo "echo foo" >/tmp/xxx bash-2.05$ /usr/bin/env - /bin/sh -c ". /tmp/xxx; echo bar &" foo bash-2.05$ bar Although the shell doesn't wait for the background process to finish, this should work just fine. -- Sam _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
