13 messages in net.sourceforge.lists.courier-users[courier-users] Re: Problem in courie...
FromSent OnAttachments
Courier UserJun 8, 2002 3:12 pm 
Courier UserJun 9, 2002 7:55 am 
Sam VarshavchikJun 9, 2002 8:10 am 
Courier UserJun 9, 2002 9:22 am 
Sam VarshavchikJun 9, 2002 10:00 am 
Courier UserJun 9, 2002 10:01 am 
Courier UserJun 9, 2002 10:14 am 
Sam VarshavchikJun 9, 2002 10:28 am 
Courier UserJun 9, 2002 10:52 am 
Juha SaarinenJun 9, 2002 1:11 pm 
Courier UserJun 9, 2002 1:29 pm 
Anand BuddhdevJun 9, 2002 2:43 pm 
Courier UserJun 9, 2002 4:38 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: Problem in courierctl.start (was: DEFAULTDELIVERY ignored [ ... ] )Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jun 9, 2002 10:00:40 am
List:net.sourceforge.lists.courier-users

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 ro@usf-cf-x86-freebsd-1.cf.sourceforge.net:/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