Thursday, December 20, 2007

W - Payload Website Mirroring

I have been testing rsync for copying files for the purpose of maintaining a true fail back mirror for HSTPLFSW on MNISUN.

1. Run options: Most of interactive runs are done by

rsync -avze ssh hstplfsw:/web/docs/payload1 /web/docs/payload1/

Notice that there is no / after the source location for a good reason. This creates a large log with the first level -v option (706,0192 bytes). The log file basically lists all the files that were "touched". For a run within cron job, it seems better to do it without -v option:

rsync -aze ssh hstplfsw:/web/docs/payload1 /web/docs/payload1/

This produces a very samll log since it supposed to list only error messages, or would it also list files where there is a change? I do not have chance to see any changes in the files yet. I just noticed that ACS has a 12/20 update. Let me just run rsync on ACS directory and see the way the file is updated and log is recorded.

2 Current rsync on hstlfsw is 2.6.5pre2, while MNISUN is running a slightly older version.
It might not be a problem, but I would like to upgrade both to newer stable versions.

3. It seems that we can install a BLOGing server on our website. I checked Apache website. Apache Roller seems quite nice and a good potential candidate. The question may be if it requires Tomcat and MySQL. That might be more work than what I can take on now.

Use my Blog for notes

It is hard the believe that I have not write anything on the BLOG for more than a year. Not that I don't have anything to write but it is not my habit to write it here.

Since this BLOG is really not public (I'll make sure that is the case), I can use it to record many areas of thoughts and progress. Just share it among friends, or people who need to know.