> Thanks for all the good ideas. My build process is not CPU > intensive, I > don't need Grid or multi processors.
Grid technology doesn't automatically imply that the process is CPU intensive. The Globus toolkit includes a lot of things that are just as useful for single systems -- batch scheduling, file location and management, and a whole lot more. Those tools are just as useful on single systems as in multi-system environment, and if you think ahead to future problems where taking advantage of multiple systems might be useful as your environment grows, the toolsets from Globus adapt trivially to additional machines (and users don't see the change). (Side note: basically, they're reinventing JES and file catalogs because they can't be bothered to spend 20 minutes in the library RTFMing about all the work done in the last 30+ years on *exactly the same topics*...mumble, frump). Same with NQS. Getting people used to doing non-interactive builds is always a good idea. > Building a propper > makfile seems the > best idea. A lockfile may be good to keep more than one > person from running > the make at a time. It (a good makefile) is also the first step to any of the more automated solutions, so you won't be wasting time or energy. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
