Tivoli

[Franz Wolfhagen]

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/