lt;>
> To:
> Sent: Friday, June 06, 2008 4:16 AM
> Subject: Re: Patch to allow Cron to use non-POSIX shells like Powershell.exe
> and CMD.exe
>
>
> | On further investigation, it appears powershell does alias "-c" for
> | "-command" hence no changes w
Christopher Faylor wrote:
Mr. Vixie rightly assumed that cron was running in a UNIX-like
environment where shells take the "-c" option. Ditto the authors of
"make", "vim", and other packages which use the SHELL environment
variable.
Can we please put this to rest now?
012345678901234567890123
- Original Message -
From: "Blair Sutton" <>
To:
Sent: Friday, June 06, 2008 4:16 AM
Subject: Re: Patch to allow Cron to use non-POSIX shells like Powershell.exe
and CMD.exe
| On further investigation, it appears powershell does alias "-c" for
| "-com
On Fri, Jun 06, 2008 at 09:16:41AM +0100, Blair Sutton wrote:
>On further investigation, it appears powershell does alias "-c" for
>"-command" hence no changes would be required for cron to support it.
>However, the change would still be useful for other shells or perhaps
>interpreters like Perl.
>
On further investigation, it appears powershell does alias "-c" for
"-command" hence no changes would be required for cron to support it.
However, the change would still be useful for other shells or perhaps
interpreters like Perl.
On Pierre's offered solution: I now do recall how exec works and i
Christopher Faylor wrote:
Cygwin endeavors to present
an environment where shells understand "-c" rather than "/c".
I did not look at the change. My initial gut reaction
on that change was...no way..."/" is a path character, and it's
because Bill Gates wanted to look different fro
On Thu, Jun 05, 2008 at 12:47:42PM -0700, Linda Walsh wrote:
> Blair Sutton wrote:
>> Eric Blake <[EMAIL PROTECTED]> writes:
>>>Why should we patch a cygwin utility to promote the use of a non-cygwin
>>>shell?
>
>None of the shells are 'cygwin', really, -- they are shells that took
>their ideas fro
On Thu, Jun 05, 2008 at 06:43:25PM -0400, Mark J. Reed wrote:
>The sh process is not "extra" since it's replaced by the powershell
>process, right? Unless "exec" works differently in Cygwin, which is
>entirely possible
Nope, you're right. It is replaced as long as it isn't the top-level
cygwi
The sh process is not "extra" since it's replaced by the powershell
process, right? Unless "exec" works differently in Cygwin, which is
entirely possible
As a solution it seems reasonable to me... I'd much rather use a
configuration-based change than worry about maintaining a patch. But
that'
I'm not sure if that's a very good solution. It spawns an unnecessary
bourne shell process on each new cron job.
Don't worry if you don't want to make the change. I will maintain my
own separate branch and perhaps post the patch with some instructions
somewhere online where other people may find i
- Original Message -
From: "Blair Sutton" <>
To:
Sent: Wednesday, June 04, 2008 12:48 PM
Subject: Patch to allow Cron to use non-POSIX shells like Powershell.exe and
CMD.exe
| Hi
|
| This is a very simple patch for Cron to allow one to use a shell like
| powershell or cmd. I've done s
Blair Sutton wrote:
Eric Blake <[EMAIL PROTECTED]> writes:
Why should we patch a cygwin utility to promote the use of a non-cygwin shell?
---
None of the shells are 'cygwin', really, -- they are shells that
took their ideas from close-source Bell-Labs research. But before they
became
Eric Blake <[EMAIL PROTECTED]> writes:
> Why should we patch a cygwin utility to promote the use of a non-cygwin shell?
To increase/improve productivity. To move along with the times.
No one can argue that Powershell isn't a good shell taking some of the
best features of many popular shells befo
Blair Sutton googlemail.com> writes:
>
> I simply introduce a new environment variable called SHELLSWICTH that
> defaults to "-c" if not used. Otherwise, one can set it to "/c" or
> "-Command" for Windows shells.
Why should we patch a cygwin utility to promote the use of a non-cygwin shell?
>
14 matches
Mail list logo
