On Tue, May 29, 2007 at 06:36:07PM -0500, William Rowe wrote:
I'm retracting my two proposed choices and going with Option #3 :) Does
anyone object to Jeff's weird proposal below? I think it's the best of
both worlds.
*Guessing* whether the user wants to use a shell based on some syntactic
Joe Orton wrote:
On Tue, May 29, 2007 at 06:36:07PM -0500, William Rowe wrote:
I'm retracting my two proposed choices and going with Option #3 :) Does
anyone object to Jeff's weird proposal below? I think it's the best of
both worlds.
*Guessing* whether the user wants to use a shell based
I'm retracting my two proposed choices and going with Option #3 :) Does
anyone object to Jeff's weird proposal below? I think it's the best of
both worlds.
Speak up before I hack this in.
Bill
William A. Rowe, Jr. wrote:
Jeff Trawick wrote:
On 5/23/07, William A. Rowe, Jr. [EMAIL PROTECTED]
On May 23, 2007, at 4:39 PM, William A. Rowe, Jr. wrote:
[ ] Revert to |foo to invoke foo, and
add |$foo syntax to launch foo via sh
I like this one the best, since it consumes fewest resources in the
default case.
[ ] Retain |foo to invoke foo through sh, and
add ||foo
On Wed, May 23, 2007 at 06:39:48PM -0500, William Rowe wrote:
While I'm working on a solution to permit cmd.exe to be launched from
a service process within Win32, I'm still struck by the inefficiency
here and feel we need to resolve the core issue.
...
[ ] Revert to |foo to invoke foo, and
On 5/23/07, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
While I'm working on a solution to permit cmd.exe to be launched from
a service process within Win32, I'm still struck by the inefficiency
here and feel we need to resolve the core issue.
Regarding the inefficiency, it doesn't seem to
On 05/24/2007 11:27 AM, Joe Orton wrote:
On Wed, May 23, 2007 at 06:39:48PM -0500, William Rowe wrote:
While I'm working on a solution to permit cmd.exe to be launched from
a service process within Win32, I'm still struck by the inefficiency
here and feel we need to resolve the core issue.
On Wed, May 23, 2007 at 06:39:48PM -0500, William A. Rowe, Jr. wrote:
So I brought up to the list 'fixing' this with an additional meta
character to follow | that would distinguish sh from non-sh invocations,
and permit both.
Wouldn't | exec logger work?
--
Colm MacCárthaigh
On 05/24/2007 02:39 PM, Colm MacCarthaigh wrote:
On Wed, May 23, 2007 at 06:39:48PM -0500, William A. Rowe, Jr. wrote:
So I brought up to the list 'fixing' this with an additional meta
character to follow | that would distinguish sh from non-sh invocations,
and permit both.
Wouldn't |
On May 24, 2007, at 4:04 AM, Sander Temme wrote:
On May 23, 2007, at 4:39 PM, William A. Rowe, Jr. wrote:
[ ] Revert to |foo to invoke foo, and
add |$foo syntax to launch foo via sh
I like this one the best, since it consumes fewest resources in the
default case.
[ ] Retain
Jeff Trawick wrote:
On 5/23/07, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
While I'm working on a solution to permit cmd.exe to be launched from
a service process within Win32, I'm still struck by the inefficiency
here and feel we need to resolve the core issue.
Apparently it is a good
William A. Rowe, Jr. wrote:
While I'm working on a solution to permit cmd.exe to be launched from
a service process within Win32, I'm still struck by the inefficiency
here and feel we need to resolve the core issue.
FYI - Paul asked on httpd about the discussion; see
12 matches
Mail list logo
