On Fri, Jan 11, 2002 at 10:19:57AM -0800, Andrew DeFaria wrote:
> >
> >
> >On Thu, Jan 10, 2002 at 10:45:27AM -0800, Andrew DeFaria wrote:
> >
> >>limits" to cron. IOW I guess what I'm saying is that *something* should be
> >>done (I know you can see this as whining and perhaps it is. But it's
>
>
>
>On Thu, Jan 10, 2002 at 10:45:27AM -0800, Andrew DeFaria wrote:
>
>>limits" to cron. IOW I guess what I'm saying is that *something* should be done (I
>know you can see this as whining and perhaps it is. But it's whining for a good
>cause! :-)
>>
>So, why aren't you going to roll up your sl
On Thu, Jan 10, 2002 at 10:45:27AM -0800, Andrew DeFaria wrote:
> limits" to cron. IOW I guess what I'm saying is that *something* should
> be done (I know you can see this as whining and perhaps it is. But it's
> whining for a good cause! :-)
So, why aren't you going to roll up your sleeves an
You wrote:
>At 01:45 PM 1/10/2002, Andrew DeFaria wrote:
>>Anyway, cron has no access to them. It's running under SYSTEM
>>account which has only access to publicly available net
drives, that
>>is, drives which are available w/o any form of authe
At 01:45 PM 1/10/2002, Andrew DeFaria wrote:
>Anyway, cron has no access to them. It's running under SYSTEM
>account which has only access to publicly available net drives, that
>is, drives which are available w/o any form of authentication
>required.
>No credentials, no au
Anyway, cron has no access to them. It's running under SYSTEM
account which has only access to publicly available net drives, that
is, drives which are available w/o any form of authentication
required. The forked cron jobs are running in the same logon session
even if they ar
On Wed, Jan 09, 2002 at 07:29:50PM -0800, Andrew DeFaria wrote:
> Larry Hall (RFK Partners, Inc) wrote:
>
> >OK, yes all your mounts are system. Looking back over your original
> >comments, what doesn't work again? You seem to indicate that cron is
> >running. The output you show indicates
Larry Hall (RFK Partners, Inc) wrote:
>OK, yes all your mounts are system. Looking back over your original comments, what
>doesn't work again? You seem to indicate that cron is running. The output you show
>indicates it did run. But you claim it didn't run a script. How did you determine
At 06:25 PM 1/9/2002, Andrew DeFaria wrote:
>Larry Hall (RFK Partners, Inc) wrote:
>
>>At 05:06 PM 1/9/2002, Andrew DeFaria wrote:
>>
>>>I've set up cron on my desktop according to /usr/doc/Cygwin/cron.README which
>states I should:
>>>
>>>$ cygrunsrv -I cron -p /usr/sbin/cron -a D -e "CYGWIN=nts
Larry Hall (RFK Partners, Inc) wrote:
>At 05:06 PM 1/9/2002, Andrew DeFaria wrote:
>
>>I've set up cron on my desktop according to /usr/doc/Cygwin/cron.README which states
>I should:
>>
>>$ cygrunsrv -I cron -p /usr/sbin/cron -a D -e "CYGWIN=ntsec"
>>$ cygrunsrv -S cron
>>
>>And I have the follo
At 05:06 PM 1/9/2002, Andrew DeFaria wrote:
>I've set up cron on my desktop according to /usr/doc/Cygwin/cron.README which states
>I should:
>
>$ cygrunsrv -I cron -p /usr/sbin/cron -a D -e "CYGWIN=ntsec"
>$ cygrunsrv -S cron
>
>And I have the following crontab installed:
>
>15 * * * * echo -e "D
I've set up cron on my desktop according to /usr/doc/Cygwin/cron.README
which states I should:
$ cygrunsrv -I cron -p /usr/sbin/cron -a D -e "CYGWIN=ntsec"
$ cygrunsrv -S cron
And I have the following crontab installed:
15 * * * * echo -e "Debugging cron $(date)\n">
/tmp/cron
12 matches
Mail list logo
