Client Server Imaging.

23 10 2006

Finally I stuck on a solution for the same. Why not have another file which will store the name of the previous image installed and then whenever we go towards installing the next image this previous image name is read out and compared to the one existing in the Client-Server mapping file.
The logic was simple and the implementation even simpler. I seem to be making progress in C and reviving my old skill set a lot.

The limitations of this approach. Currently, I can see one only, which is when we have two system simultaneously starting off and one is a server or both are server images. Then, if between the time frame that one finishes and the second starts, no machine is free to load the image, we might face a situation wherein the first server that finished imaging will never have the client load, as the last image file will be overwritten. Need to find something to circumvent this problem.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: