[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Re: Condor - Windows - DLL problems
- Date: Tue, 15 Mar 2005 16:35:58 -0500 (EST)
- From: Ravi Krishnan Venkatesan <rkvenkat@xxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Re: Condor - Windows - DLL problems
Thanks for your reply.
Is it necessary to have the same cygwin version in all the windows
machines in the pool?
Currently, all the machiens in the pool have cygwin version 1005.12.0.0 or
lower. I added a couple of new machines with cygwin 1005.13.0.0 and if I
try to use this new version of cygwin, then I get this error (wsock32).
On Tue, 15 Mar 2005, Matt Hope wrote:
> On Tue, 15 Mar 2005 13:48:56 -0500 (EST), Ravi Krishnan Venkatesan
> <rkvenkat@xxxxxxxxxxxxxx> wrote:
> > Yes, I do have this path set in my Environment. I also send the required
> > DLL i.e. cygwin1.dll as part of the transfer_input_files = ...
> > & I also have read & execute permissions for everyone for all the files in
> > use.
> > I still get the same error.
> I seriously doubt that attempting to use cygwin as something that can
> just be dropped in as a dll will work.
> When I use it I explicitly ensure that cygwin is installed on every
> execute machine in a well defined place with local access then any
> submitting job uses that knowledge to fire up bash (or shell of your
> choice) and get going in inixlike land.
> I strongly suggest you use this approach if posible, it makes a lot of
> issues just go away.