Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Problem running runmqsc from cron Date: Fri, 21 May 2004 10:43:37 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Harig, Mark" To: "Mike Kenny - BCX - Mngd Services" , X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i4LEjbwD016473 > -----Original Message----- > From: Mike Kenny (email address deleted) > Sent: Friday, May 21, 2004 5:15 AM > To: cygwin > Subject: Problem running runmqsc from cron > > > I have written a number of scripts to monitor queue depth and > channel status on my MQ server. These work fine from the > command line, but when I try to execute them from cron the > sciripts are executed, but the runmqsc command reports that > it can't connect to the queue manager. Has anybody come > across this or similar problems? If so how were they > resolved? (I hace searched the archives, but can find no > reference to this type of problem) > You might try examining your environment variables: * * * * * /usr/bin/env > /tmp/env.txt The environment variable settings that are set by default within cron is a limited set. For more information, see "man 5 crontab". -- 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/