#14436 closed enhancement (fixed)
Document how to work around blocked rsync port
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | markd@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | guide | Version: | 1.6.0 |
Keywords: | Cc: | ||
Port: |
Description
People often ask on the lists how they can selfupdate and sync if their network administrators have blocked the rsync port. This is worthwhile information to include in the guide. I just explained what needs to be done on the list. Maybe this can be transformed into something that can be used in the guide.
http://lists.macosforge.org/pipermail/macports-users/2008-February/009129.html
Change History (6)
comment:1 Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | Document how to work around rsync port blocked by network admins → Document how to work around blocked rsync port |
---|
comment:2 Changed 17 years ago by markd@…
comment:3 Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)
I thought about that too. Maybe it would fit into the how-to section.
comment:4 Changed 17 years ago by reiffert@…
I once were using an ssh tunnel and changed sources.conf to ask on localhost. Works as well.
Kind regards Thomas
comment:5 Changed 16 years ago by raimue (Rainer Müller)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:6 Changed 16 years ago by (none)
Milestone: | Website & Documentation |
---|
Milestone Website & Documentation deleted
Note: See
TracTickets for help on using
tickets.
I think this might be better on the wiki, because I can see many similar entries on this down the road. But in any case, it someone would reduce it to concrete steps (step 1, step 2, ...) it would be the first step to documenting it wherever it ends up.