Rob wrote:
Matthew Farrellee <matt@xxxxxxxxxx> wrote:
Sounds like you've run into a somewhat known problem. It is true that
Condor can start and check for VMware before VMware has a chance to
start itself. I believe a proposed fix for this is to actually let the
startd check for VMware periodically, if it isn't present, instead of
only once at startup.
I'm little confused by your suggestion....
Is this a fix I can apply in my configuration?
Can I let startd check periodically for VMware by setting
one of the macros? I suppose not.
What you suggest here sounds more like a necessary patch to
the program source code to add your "new feature" into a
future release.....I would be very happy if that happens!
This problem actually makes VMware + Condor on a large pool
of Windows PCs not workable. I plan to have this setup on 500+
library PCs, which boot up every morning after their nightly
shutdown.
Of course I can manipulate the Windows configuration such that it
restarts condor some time after the reboot; but I hope that this
is not necessary.
Rob.
Yes, I was not suggesting that as a workaround.
For a workaround, if you can configure Windows to start VMware before
Condor you may have some luck, otherwise you'll have to delay the start
of Condor in some other way. In the Linux world this is pretty easy to
achieve. On Windows, I believe some may have turned the Condor start
script into a batch file to introduced delays.
Best,
matt
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to
condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-usersThe archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}