Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: cron as service problem with OLE application
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0307111222170 DOT 6088-100000 AT slinky DOT cs DOT nyu DOT edu>
From: jmadams AT monkeybean DOT dyndns DOT org (John M. Adams)
Date: Thu, 17 Jul 2003 14:51:53 -0400
In-Reply-To: <Pine.GSO.4.44.0307111222170.6088-100000@slinky.cs.nyu.edu> (Igor
 Pechtchanski's message of "Fri, 11 Jul 2003 13:00:22 -0400 (EDT)")
Message-ID: <m37k6hnfzq.fsf@monkeybean.dyndns.org>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Common Lisp, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu> writes:

> On Fri, 11 Jul 2003, John M. Adams wrote:
>
>> Dear Friends,
>>
>> I have this odd problem with the latest cron.  cron_diagnose seems to
>> think everything is fine.  I followed the instruction for reinstalling
>> cron as a service.  The service is set to interact with desktop.
>>
>> I want to run a perl (non-cygwin) script that starts a gui application
>> and manipulates it via an OLE interface.  The application is for
>> downloading financial data (CSI UA).
>>
>> When cron is running as a service, the application starts, the GUI
>> comes up, but it does not start the update (as requested via OLE).
>>
>> If I start cron from a shell.  The application works as expected.
>>
>> Any clues?
>> Thanks a lot.
>
> Well, the one obvious difference is that cron as service runs from another
> account (SYSTEM).  Another could be that the mount points and environment
> are different inside the application.  Try adding "env > /tmp/env" and
> "mount -m > /tmp/mounts" as one-time commands to your crontab and
> comparing the output to that of the same commands run from a shell -- that
> might provide some clues.  If all else fails, you could try to run cron
> from a SYSTEM-owned shell and see if that makes a difference.  To get a
> SYSTEM-owned shell, you could use the "at /interactive" trick (search the
> archives for an example).

The env differs in that the cron process has LOGNAME, TZ, and SHELL.
There is no difference in mounts.  For grins, I unset those variables
in my script, but that had no effect.

Running cron from a system owned shell gives behavior identical to
running under the cron service running as system.

-- 
John M. Adams

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/