On 2014-10-21 18:39, Rolf Huehne wrote: > It is not that simple. > The current user might not have the right to write in the install > directory. > What about multiple users on the same computer?
Hi Rolf, You are right. Then the choice of the directory requires more consideration, but I am sure it is not an unsolvable problem. > One set of problems here will be caused by multiple instances of Jmol > run simultaneously by the same user on the same computer. > If you write one line at a time you will get a mixture of different > sessions that will not be very helpful. You must also make sure that > the > instances are writing one after another. Good point again. Writing a single history file by multiple instances should never ever happen. > And what about command-line usage? > We use Jmol.jar for example for producing automatically about 300000 > images for all PDB structure by a complex script with about hundred > lines of code. I wouldn't want that to be slowed down by writing into a > history file for each line (and coordinating to do this from 30 > processes in parallel). Your massive use case and a usual simple experimenting differ a lot. I still think that a history file across multiple sessions is of great value while one is experimenting with Jmol. In "expert mode" is should be just switched off completely. Gabor ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
