i had built a dual-boot NT / linux cluster
at my previous job. there was an mpi forNT at that time and i used a samba server to unify
user homes across all the machines and both OS'es.
we had a similar experience with microsoft, but they were trying to throw hardware at us to keep
the cluster "NT only". Opensource tools like samba , VNC, and MPI, were instrumenta in the functioning of the NT cluster. On of the biggest annoyances occured when a job would crash and the mpi would call win32 to create a window with an error message. The shameful aspect was that the processes on that machine could not be killed remotely until someone went and clicked off those
annoying error windows! The kill command in the reskit failed to stop those processes since they were being blocked in the win32 part of the kernel! (at least i think so).
Slashdot Mirror
i had built a dual-boot NT / linux cluster at my previous job. there was an mpi forNT at that time and i used a samba server to unify user homes across all the machines and both OS'es. we had a similar experience with microsoft, but they were trying to throw hardware at us to keep the cluster "NT only". Opensource tools like samba , VNC, and MPI, were instrumenta in the functioning of the NT cluster. On of the biggest annoyances occured when a job would crash and the mpi would call win32 to create a window with an error message. The shameful aspect was that the processes on that machine could not be killed remotely until someone went and clicked off those annoying error windows! The kill command in the reskit failed to stop those processes since they were being blocked in the win32 part of the kernel! (at least i think so).