public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Harig, Mark" <maharig@idirect.net>
To: "Mike Kenny - BCX - Mngd Services" <Mike.Kenny@bcx.co.za>,
	<cygwin@cygwin.com>
Subject: RE: Problem running runmqsc from cron
Date: Fri, 21 May 2004 15:11:00 -0000	[thread overview]
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E014598B5@ex02.co.idirect.net> (raw)



> -----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/

             reply	other threads:[~2004-05-21 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21 15:11 Harig, Mark [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-24  9:54 Mike Kenny - BCX - Mngd Services
2004-05-21 11:14 Mike Kenny - BCX - Mngd Services

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BADF3C947A1BD54FBA75C70C241B0B9E014598B5@ex02.co.idirect.net \
    --to=maharig@idirect.net \
    --cc=Mike.Kenny@bcx.co.za \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).