This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[members-discuss] RIPE DB NRTM access.
- Previous message (by thread): [members-discuss] RIPE DB NRTM access.
- Next message (by thread): [members-discuss] RIPE DB NRTM access.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrea Cocito
andrea.cocito at ifom-ieo-campus.it
Sat Jan 7 22:07:40 CET 2012
On Jan 7, 2012, at 9:14 PM, Pawel Tyll wrote: >> My guess would be that a full snapshot available via ftp is >> considered not that NEAR Real Time as the update data stream that >> you may pull continuously from the server - they're not trying to >> sell data there but the service of that data being streamed. > I don't need to pull it continuously. It can even be limited to one > connection a day, although again, I see no reason for such > limitations. I would only like a local mirror that I can hammer > however frequently I wish, that would be relatively up-to-date. I can > pull the snapshot once a day, restart irrd and be done with it, > but...that's just wrong :) Hi, maybe a simple rsync server would do the job for you and for everyone else with similar needs (described as "I need a periodic update but I don't really need a realtime one"). At our site we mirror a few terabytes of data (genomic repositories) via rsync without even noticing an impact of bandwidth usage (as long as only a small part of those big files changes every day). Anyone at RIPE willing to consider this option ? Ciao, A.
- Previous message (by thread): [members-discuss] RIPE DB NRTM access.
- Next message (by thread): [members-discuss] RIPE DB NRTM access.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]