From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12388 invoked by alias); 24 May 2004 06:37:19 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 12343 invoked from network); 24 May 2004 06:37:16 -0000 Received: from unknown (HELO wamid01.africa.enterprise.root) (196.29.130.201) by sourceware.org with SMTP; 24 May 2004 06:37:16 -0000 Received: from EXMID04.africa.enterprise.root ([172.21.31.140]) by wamid01.africa.enterprise.root with Microsoft SMTPSVC(5.0.2195.6713); Mon, 24 May 2004 08:37:45 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Problem running runmqsc from cron Date: Mon, 24 May 2004 09:54:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Mike Kenny - BCX - Mngd Services" To: "Harig, Mark" , X-OriginalArrivalTime: 24 May 2004 06:37:45.0714 (UTC) FILETIME=[9F80F520:01C44159] X-IsSubscribed: yes X-SW-Source: 2004-05/txt/msg00779.txt.bz2 > > I have written a number of scripts to monitor queue depth and=20 > > channel status on my MQ server. These work fine from the=20 > > command line, but when I try to execute them from cron the=20 > > sciripts are executed, but the runmqsc command reports that=20 > > it can't connect to the queue manager. Has anybody come=20 > > across this or similar problems? If so how were they=20 > > resolved? (I hace searched the archives, but can find no=20 > > reference to this type of problem) > >=20 >=20 > You might try examining your environment variables: >=20 > * * * * * /usr/bin/env > /tmp/env.txt >=20 > The environment variable settings that are set by > default within cron is a limited set. For more > information, see "man 5 crontab". >=20 Thanks Mark. I had actuallly dumped my environment from within cron and compared it. It seemed OK. I found an explanation of the problem by googling. For those who may be interested, the issue is that cron has to su to execute the jobs for each user. As cygwin is cannot use NT to authenticate the user, any job that is going to be executed on behalf of that user must not use any resource that will require authentication. -- 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/