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: cron problem with authentication Date: Wed, 26 May 2004 09:52:27 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Mike Kenny - BCX - Mngd Services" To: "Cygwin (E-mail)" X-OriginalArrivalTime: 26 May 2004 07:52:28.0009 (UTC) FILETIME=[63FC6590:01C442F6] X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i4Q7qh9A004249 I previously posted a problem where a job failed attaching to an MQ Q Manager when run from cron. The explanation that was provided was that because MQ authenticates the user using the NT services and cron had had to su to that user, bypassing these services, that the user running the job did not then have the correct credentials. This sounds plausible and certainly explains the behaviour I see, but what would be involved in cron checking to see under which user the cygwin session is running and if this is the same user as the cygwin cron service is running under. If they are the same then do not do the change of user? Would this enable the cron job to run with the correct credentials? Or am I totally misunderstanding the problem? I admit that I know little or nothing about either Windows security or how cygwin interacts with it. Thanks for any comments on this -- 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/