Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
In-Reply-To:	<F0D7281DAB048B438E8F5EC4ECEFBDDC1760B2@esmail.elsag.de>
Subject:	RE: Tivoli
To:	cygwin AT cygwin DOT com
Message-ID:	<OFEBE8C09F.FBA1FC22-ONC1256EB0.0032DCC1-C1256EB0.00335B08@dk.ibm.com>
From:	Franz Wolfhagen <FRANZW AT dk DOT ibm DOT com>
Date:	Fri, 11 Jun 2004 11:23:55 +0200
MIME-Version:	1.0
X-IsSubscribed:	yes

You are right that that is what is described there - I do not know why this
is not a problem with the tivoli dll's (they may be so old that they do not
use the shared memory segment ?) - but is not a problem in this specific
case.

I am not happy with the statement in the faq - but me gut feeling is that
people that work with both tivoli and cygwin normally knows a lot more than
"normal" users do.

The problem ofcourse can be where users monitored via tivoli software
includes their non-tivoli cygwin1.dll in the path in such a way that this
interferes with the tivoli software utilities - but I am not sure this is
really a problem either (I have not tested it).

I can only give on advice - if you are having problem with this combination
- you should not use this mailing list to blame cygwin....

Med venlig hilsen / Regards
Franz Wolfhagen


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

- Raw text -