Archive for August 2009
For all @ FIT in aid of ASE subject tomorrow. Hope this helps..
A clock synchronization algorithm used to synchronize the time on a machine with a remote time server. This is a very straightforward algorithm, and is quite easy to understand.
- A process p requests the time in a message mr and receives the time value t in a message mt.
- t is inserted in mt at the last possible point before transmission from the server S.
- Tround = Time(send mr) + Time ( receive mt) = (1-10)*10-3 seconds on a LAN.
- min = minimum queueing time for S.
The earliest point at which S could have placed the time mt was min after p dispatched mr. The time by S’s clock when the message is received by P is in the range
t + min < p < t + Tround - min. The total width of this range is
Tround - 2*min. This gives an accuracy of (Tround / 2 – min). If all of that made absolutely no sense to you, here’s a much simpler (but far less rigorous) explanation. Basically, the client sends a request for the current time to the time server. When it receives the response, it finds the transmission delay (time between the request being sent and the response being received), divides that in half, and adds that to the time received back from the server. The idea is to eliminate the inaccuracy caused by network delays. This assumes that the link is equally fast both ways, which may not always be the case. But as with any algorithm, you have to make tradeoffs.
A distributed clock synchronization algorithm, developed by Drs. Gusella and Zatti at the University of California, Berkeley in 1989.
Here’s what you do:
Choose a coordinator computer to act as the master. The master periodically polls the slaves whose clocks are to be synchronized to the master. The slaves send their clock values to the master.
The master observes the transmission delays and estimates their local clock times. Once this is done, it takes a fault-tolerant average of all the times including its own, and ignores those that are far outside of the range of the rest.
The master then sends each slave the amount (positive or negative) that it should adjust its clock. This is very ingenious, because it means that it doesn’t have to send absolute times (which will be messed up by network delays
Start of a new era in the Faculty. We (Me, Laknath, Lakshan) along with three other speakers pushed the wheel to inaugurate the Free n Open Source Software community in the faculty. This was a need which the previous batches tried to establish but were in vein to a reason unknown. But now its all history.
With the latest intake (FIT-B9), and with the new curriculum, we showed them a new pathway to adjust their future. This project unveils our potential in the FOSS movement and support we can give as The Faculty of IT.
To be frank, this post is the first time I am using Firefox on Ubuntu 9.04 (which I just received with another Kubuntu CD). I am not seriously into FOSS stuff yet but with the new project and the new CDs its kind of itching for me. 😛
Well the next steps would be after our examinations, Level 3 Semester 2. We intend to set up a new FOSS resarch lab with the faculty along with other infrastructure changes we need for the students. (Specially the WiFi expansion for laptop users).
Taking in some FOSS projects and encouraging our students to involve with them would be another effort if they have already been grabbed by MS. He he :P.
Well…more projects to come from my head after the FOSS@FIT. Especially the FITCOC which I need to start soon after the ASE paper. But I am in danger of been stolen “my” intellectual property. Lets hope for the best n prepare for the worst.