, Blair Sutton [EMAIL PROTECTED] wrote:
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
everyone's time with these half-baked workarounds.
Still, I am sure you mean well. Please don't bother responding. Best wishes
On Fri, Jun 6, 2008 at 5:19 PM, Pierre A. Humblet
[EMAIL PROTECTED] wrote:
- Original Message -
From: Blair Sutton
To: cygwin
Sent: Friday, June 06, 2008 4:16 AM
what you want.
And what's wrong with doing this with what cron already provides:
* * * * * /cygdrive/c/windows/system32/windowspowershell/v1.0/powershell -
Command 'c:\documents and settings\blair sutton\my
documents\windowspowershell\test\test.ps1 one two three'
This doesn't work. Have you
it useful.
Best regards
Blair
On 6/5/08, Pierre A. Humblet [EMAIL PROTECTED] wrote:
- Original Message -
From: Blair Sutton
To: cygwin
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
for Windows shells.
Typical usage is
#SHELL=/cygdrive/c/WINDOWS/system32/CMD.exe
#SHELLSWITCH=/c
SHELL=/cygdrive/c/WINDOWS/system32/windowspowershell/v1.0/powershell.exe
SHELLSWITCH=-Command
* * * * * echo test 1 2 3
* * * * * ls c:
* * * * *'C:\Documents and Settings\blair sutton\My
Documents
5 matches
Mail list logo