Apache OpenOffice (AOO) Bugzilla – Issue 7802
Description for using symlinks; & warning
Last modified: 2004-03-22 16:09:49 UTC
Hi As we discussed, we'd like to reorganize the files on CN mirrors to /stable, /developer, etc., and use, in transition, symbolic links. During this period, the mirrors will need to be counseled that things are okay and that we don't have duplicate items. I am unfamiliar with how to request CN ops to create the symlinks. Would you be able to draft a short statement I can then file with Ops? As well, handle the mirrors discussion? I would like this to be done before Tuesday. Thanks louis
in progress, will send via email in a second, minute, ...
part 1 (statement for ops) done. If I don't get feedback about the prefered method from you (or ops) I will go ahead with a vage warning to the mirrors list on tuesday.
Hi Posted PCN issue to Ops and have asked for opinion. thanks louis
message sent to mirrors.
Hi, reopening to report progress. From Ops IZ 11787: "all the hard links have been made and have been rsync'd. let me know when they are ready to have the old stuff removed." awaiting your indication. -cheers, louis
OK, so, it might be time to reassign to support :-( Directories below http://ny1.mirror.openoffice.org/stable/ are empty. Is the sync still ongoing?
will check on this. louis
reassigning to support. sf1 does have the directories. But just checked at 11:40 and ny1 still does not have the files in the directories. Kenneth/Brian: this seems to be a version of IZ 7853. Please coordinate with ops to make sure that ny1--the primary mirror server--has the files. thanks Louis
hi, a new development: /developer seems to be read only. it must be write, too. K, B, is this an artifact of the rsync process? thanks louis
Please check the /developer directory now.
Hi, /developer is ok - that was issue 7924. The synchronisation between ny1/sf1 seems finished.
I was responding about /developer to Louis's comment in this issue. Closing.
As agreed by Louis I will close these resolved fixed support-owned issues now. If you have trouble with that, please re-open the issue.
For technical reasons we have to move the issue to another subcomponent tan 'www'. Sorry for bothering you with this generated notification message. There is no need for any action from yor side. Thanks for your understanding, Stefan