Problem solved: Re: time.sleep(1) sometimes runs for 200 secondsunder windows

P

Paul Probert

Thanks everyone for your help.
It was the "Abouttime.exe" program, a time synch utility. To get the
problem, you have to run it as a service, and possibly it has to have
trouble connecting to its time servers. It would cause time.sleep(1) to
sometimes block for 200 seconds. Not "about" 200 seconds but always
within 199 to 202 seconds. Very strange, but it is good to have the
problem gone.

Enjoy the weekend!

Paul Probert
University of Wisconsin
 
M

Magnus Lycka

Paul said:
Thanks everyone for your help.
It was the "Abouttime.exe" program, a time synch utility. To get the
problem, you have to run it as a service, and possibly it has to have
trouble connecting to its time servers. It would cause time.sleep(1) to
sometimes block for 200 seconds. Not "about" 200 seconds but always
within 199 to 202 seconds. Very strange, but it is good to have the
problem gone.

So did you understand what happened? Was the system call time.time()
just hanging while abouttime.exe was synching time?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,756
Messages
2,569,535
Members
45,008
Latest member
obedient dusk

Latest Threads

Top