diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-July/003793.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-July/003793.html | 116 |
1 files changed, 116 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-July/003793.html b/zarb-ml/mageia-sysadm/2011-July/003793.html new file mode 100644 index 000000000..81350adcf --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-July/003793.html @@ -0,0 +1,116 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Update procedure on sysadmin side + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Update%20procedure%20on%20sysadmin%20side&In-Reply-To=%3C20010.5341.154831.856900%40fisica.ufpr.br%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003792.html"> + <LINK REL="Next" HREF="003769.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Update procedure on sysadmin side</H1> + <B>Carlos Carvalho</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Update%20procedure%20on%20sysadmin%20side&In-Reply-To=%3C20010.5341.154831.856900%40fisica.ufpr.br%3E" + TITLE="[Mageia-sysadm] Update procedure on sysadmin side">carlos at fisica.ufpr.br + </A><BR> + <I>Sat Jul 23 02:25:01 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003792.html">[Mageia-sysadm] Update procedure on sysadmin side +</A></li> + <LI>Next message: <A HREF="003769.html">[Mageia-sysadm] rpmlint check on upload, attempt 2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3793">[ date ]</a> + <a href="thread.html#3793">[ thread ]</a> + <a href="subject.html#3793">[ subject ]</a> + <a href="author.html#3793">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael scherer (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>) wrote on 22 July 2011 23:37: + >> Should we hardlink the rpms instead of moving them, + >> and postpone the removal from *_testing for a few days (or ~a week) + >> so all mirrors catch up... + >> + >> That would save the mirrors from re-downloading the stuff, and make + >> the updates available faster... + > + >> It does not matter much for a simple update like logrotate, but a + >> kernel update or a full kde update would definately benefit from it. + > + >I think that's negligeable when compared to the size of cauldron updates, + >and that would be slightly more complex to develop. + > + >This would also mean we keep then in updates_testing, thus having bigger + >hdlists, which mean more rpms to parse, and more data to download by mirror + >( since hdlists are redownloaded each time, since they are compressed and + >I am doubtful about the rsync-friendliness of the whole compression ). + +Depends on the type of compression you use. In general compression +produces cumulative changes and thus spoils rsync's economy. However if +you use gzip you can do gzip --rsyncable and preserve rsync +efficiency. --rsyncable is a separate patch to gzip; Debian has it. +If one wishes high compression then xz should be used, not gzip. + + >And since hdlists are downloaded by every users doing testing, it may have a + >bigger impact. + +I'm not sure what hdlists mean. If it's file lists it'll be +negligible. OTOH, if users have to download full file lists each time +you have more urgent problems than the extra hardlinks, you should +make available diffs to these lists like Debian does. Otherwise users +may end up downloading more bureaucracy stuff than what's important for +them... + +For mirrors sending a little extra is no problem. The advantage of +propagating changes faster and doing less disk writes is much more +important. + + >> the downside is of course more complex code on staging/primary mirror + > + >Yes, and I fear this may not be so trivial to do (ie, how do we know + >that we need to remove a rpm from update_testing, since we cannot + >base on the creation date due to the hardlink ) + +How about creating a list of the names that are hard linked instead of +removed at each master update? You can simply log-rotate it and +each cycle will just remove the names in the Nth one. Doesn't look +very complex. With N=2 or 3 you'll cater for the vast majority of +mirrors. +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003792.html">[Mageia-sysadm] Update procedure on sysadmin side +</A></li> + <LI>Next message: <A HREF="003769.html">[Mageia-sysadm] rpmlint check on upload, attempt 2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3793">[ date ]</a> + <a href="thread.html#3793">[ thread ]</a> + <a href="subject.html#3793">[ subject ]</a> + <a href="author.html#3793">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |