Question: It sounds like you're trying to kill off users.o.o completely, migrating to connect.o.o. Is that really necessary? There is ordinarily no reason why a resource can't be known by multiple names. IMO a more graceful way is to add the new sub-domain without removing the old one. This likely would have to be done at the main DNS records and secondarily at any place which might be configured at the app (eg. webserver or individual app) where necessary. I would then assume that the next step is to re-configure as many links you have access to, to use the new domain name instead of the old. Then followup by periodically parsing the standard logs to determine who continues to use the old domain name long after all newer traffic is using the new subdomain. If the traffic is little, then <maybe> messages can be sent to the link owners manually, or you can try creating an automatic solution (because I'm not aware that one already exists although might). Or, just ignore the old links, they'll "just work." IMO, Tony On Thu, May 5, 2011 at 7:27 AM, Pavol Rusnak <prusnak@opensuse.org> wrote:
On 05/05/2011 03:24 PM, Thomas Schmidt wrote:
Has someone already worked on this?
Yes, there is already working export on this, but you have to login as admin and find a link on Administators' dashboard. This is what darix didn't like and wanted to have an API call for that. That one is still pending, but should not be hard to implement ...
-- Best Regards / S pozdravom,
Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-boosters+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-boosters+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-boosters+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-boosters+help@opensuse.org