Hi Chris, Lots of things which use Python only compile that Python the first time they are used, and (if they have write permission) write the compiled code back as .pyc. This makes it much faster to start next time as there is no need to compile anything. I would guess that this is the case with coot.
Here I always run things after installing them, to make it quicker for users to subsequently use them. If you have a central installation this only needs to happen once. Best wishes, Graeme -----Original Message----- From: Mailing list for users of COOT Crystallographic Software [mailto:[email protected]] On Behalf Of Chris Richardson Sent: 12 October 2011 14:39 To: [email protected] Subject: Coot startup times We have a small but interesting problem with coot startup times. The first time a user starts coot, it will take around a minute to start up. On subsequent occasions, it will take around 30 seconds. However, if that user runs coot once with "sudo coot" all subsequent invocations will only take around 3 seconds to start up on that machine. Am I right in assuming that invoking coot with root privileges allows it to write some files somewhere that are used on subsequent runs? Could I change the permissions of the appropriate directory to allow fast startup without giving my users sudo access? Should I just tell the users to be more patient? Platform information: a variety of macs running OS X 10.6.8. Coot 0.7-pre (also 0.6 in the past) installed using fink. All accounts are network accounts with a network home directory mounted using AFP. We hot desk, so speeding up coot for all users on all machines using sudo would be a horrible task. Regards, Chris -- Dr Chris Richardson :: Sysadmin, structural biology, icr.ac.uk The Institute of Cancer Research: Royal Cancer Hospital, a charitable Company Limited by Guarantee, Registered in England under Company No. 534147 with its Registered Office at 123 Old Brompton Road, London SW7 3RP. This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer and network.
