On Fri, 12 Sep 2003, Larry Hall wrote:
> At 11:25 AM 9/12/2003, Andrew DeFaria you wrote:
> >Corinna Vinschen wrote:
> >
> >>On Thu, Sep 11, 2003 at 04:12:43PM -0700, Andrew DeFaria wrote:
> >>
> >>>Since upgrading to 1.5.3 I cannot start cron or apache as services. They
> >>>were added as follows
At 11:25 AM 9/12/2003, Andrew DeFaria you wrote:
>Corinna Vinschen wrote:
>
>>On Thu, Sep 11, 2003 at 04:12:43PM -0700, Andrew DeFaria wrote:
>>
>>>Since upgrading to 1.5.3 I cannot start cron or apache as services. They
>>>were added as follows:
>>>[...]
>>>cron : PID 3856 : starting service `cron
Corinna Vinschen wrote:
On Thu, Sep 11, 2003 at 04:12:43PM -0700, Andrew DeFaria wrote:
Since upgrading to 1.5.3 I cannot start cron or apache as services. They
were added as follows:
[...]
cron : PID 3856 : starting service `cron' failed: execv: 1, Operation
not permitted
[...]
I've just tested
On Thu, Sep 11, 2003 at 04:12:43PM -0700, Andrew DeFaria wrote:
> Since upgrading to 1.5.3 I cannot start cron or apache as services. They
> were added as follows:
> [...]
> cron : PID 3856 : starting service `cron' failed: execv: 1, Operation
> not permitted
> [...]
I've just tested it and it s
Since upgrading to 1.5.3 I cannot start cron or apache as services. They
were added as follows:
$ cygrunsrv -I cron -p /usr/sbin/cron -a -D -d "Cygwin cron" -e
"MAILTO=$USER@" -e "CYGWIN=ntsec
$ cygrunsrv -I apache -p /usr/sbin/httpd -a -k -d "Cygwin Apache" -f
"Apache for Cygwin"
$ cygrunsrv -
5 matches
Mail list logo