![](https://secure.gravatar.com/avatar/04f6f01103ff648ccc612f96fca0a8b3.jpg?s=120&d=mm&r=g)
Hi, Johannes!
I don't necessarily see the necessity to trigger every update. A rsync once a day should be sufficient, when traffic is low. Do you expect problems due to concurrent access to the (master or slave) ports tree?
Well, I was just thinking about the master. If you run triggered updates, you only have to check those ports which actually changed. If you do it in an interval, you end up checking all ports (well, pkgmk -do for a downloaded port isn't expensive but still). IOW, if there's no change in three days, you have no additional load, while at the same time you get almost instant updates when a change actually happens.
In an interval setup, you have to wait $interval (worst case), and unnecessary load every $interval if nothing changed.
Okay, understood that. I don't have the experience what's happening at crux.nu in detail (would be interesting). But I guess we think about different things now. My idea was to backup the distfiles for the corresponding ports to some server for the case that the distfiles cannot be reached anymore. The pkgmk -d can then fall back to the backup server and grab the distfiles there. That's more or less a proxy behaviour. So, we fill in missing distfiles temporarily in case the real sources are broken. Failed updates due to missing/moving/outdating URLs... are the most inconvenient experience I made with CRUX during the last years. [...]
For a particular mail alias, push incoming mail through a script; in this script, extract the svn path. Subscribe to crux-commits with this e-mail address.
We can provide a separate mailing list with an easier to parse format if that's needed.
Okay, that's a different approach. I was focused on some filesystem-level mirroring + pulled distfiles as a backup server.
Well, what's crux.nu's Size at Kalmar NDC AB? What traffic do you have there?
Well, we don't host any distfiles there, so those numbers wouldn't have any meaning in this context.
Jep, but if you multiply the average number of pulled packages/time times the average used package size we have at least some rough numbers to start with. Greets, Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm.de Phone: +49-89-741518-50 Fax: +49-89-741518-19