Jörg Schaible wrote:
> This is not recommended. http://cygwin.com/faq/faq_4.html#SEC51
>
> The cygwin core uses shared memory and it does not matter if you separate the two
> dlls with paths or rename on or ... two of these dll's will always influence each
> other - even if it is the same versi
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 feeli
Franz Wolfhagen wrote on Friday, June 11, 2004 8:39 AM:
> You will have an "extra" cygwin1.dll when running tivoli
> endpoint/managed node on the same machine as you run cygwin.
>
> I have run setups with both cygwin and 2 endpoints installed
> on the same machine - the only thing you need to tak
You will have an "extra" cygwin1.dll when running tivoli endpoint/managed
node on the same machine as you run cygwin.
I have run setups with both cygwin and 2 endpoints installed on the same
machine - the only thing you need to take care of is to NOT include the
non-tivoli cygwin dll in the pa
On 10 Jun 2004 at 22:33, Ronald van Gogh wrote:
>
> Probably it's been asked before, but I couldn't find it.
> Now I've noticed that these servers are going to be monitored with Tivoli
> and I noticed that Tivoli copied also some old cygwin files (version 1.14.2) to
> this server, although to a
On Thu, Jun 10, 2004 at 10:33:04PM +0200, Ronald van Gogh wrote:
>Probably it's been asked before, but I couldn't find it.
>I'm running on a number of servers scripts with cygwin (version 2.0.5b),
>which gather certain statistics on a application every 10 minutes. This
>seemed to work fine.
>Now
6 matches
Mail list logo
