How about using the MD5 hash of the result name and using the first 16 characters as part of the VM name?
It would look something like: boinc_A2579B43234C3456 It will look a little random to volunteers, but it will keep the names from clashing across multiple instances of BOINC running on the same machine. ----- Rom From: Lammert van der Veen [mailto:[email protected]] Sent: Friday, September 20, 2013 8:20 AM To: Rom Walton Cc: David Anderson (BOINC); Ben Segal Subject: VBoxwrapper 26026 VM-names Hello Rom, I noticed you introduced a new way to name the VM's in the newest vboxwrapper. - simple boinc__slot_x where x is the slot number. I know I'm not an average cruncher, but may attend you on the following situation: You are able to run several BOINC clients on a host with each its own BOINC data-directory Nowadays machines has tens of threads, but in principle also on a dual core it may happen. I had 8 T4T VM's running on an i7 2600 hyperthreaded and in your chosen solution for RNA long VM-names, I (and probably more vbox users) get a problem, because now we would get same VM names like boinc__slot_0. You know VirtualBox doesn't accept that. In my opinion RNA (Christian) should use shorter Work Unit names and use the VM description field for the extreme long bacteria/virus names. Kind regards, Lammert _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
