<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> Would you mind sharing some syntax examples to what you are doing? That would be helpful. Thanks.<o:p></o:p> <o:p> </o:p> # “we execute a spacewalk-clone-by-date to whatever that day is”<o:p></o:p> <o:p> </o:p> # “add a particular Errata into it” for security.<o:p></o:p> <o:p> </o:p> <table class="MsoNormalTable" border="0" cellspacing="5" cellpadding="0" align="left" width="100%" style="width:100.0%"> <tbody> <tr style="height:114.05pt"> <td width="140" nowrap="" valign="top" style="width:105.0pt;padding:3.75pt 3.75pt 3.75pt 3.75pt;height:114.05pt"> <p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:18.0pt;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly"> <o:p> </o:p> </td> <td style="padding:3.75pt 3.75pt 3.75pt 3.75pt;height:114.05pt"> <o:p> </o:p> </td> </tr> </tbody> </table> <o:p> </o:p> <o:p> </o:p> From: spacealk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com] On Behalf Of Matthew Madey Sent: Friday, September 26, 2014 8:35 AM To: glenc2004@comcast.net; spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Patch Repositories - Monthly Patching<o:p></o:p> <o:p> </o:p> <div> We create a "Baseline" channel that is sync'd nightly, so it always has the most recent patches. Then, on Patch Tuesday, we execute a spacewalk-clone-by-date to whatever that day is. We've had similar instances where a critical patch came out and our Security team wanted it in our channels immediately. With the clone channels it's simple to just add a particular Errata into it. <o:p></o:p> </div> <div> <o:p> </o:p> <div> On Fri, Sep 26, 2014 at 7:34 AM, Glen Collins <<a href="mailto:glenc2004@comcast.net" target="_blank">glenc2004@comcast.net</a>> wrote:<o:p></o:p> Hi All, I have a general question of the community on how everyone does their patching. Here is what my company does.... Update the repository once a month on Microsoft Patch Tuesday. Keep that as a baseline for the entire month so DEV, Test and Prod systems are patched exactly alike. While this works pretty well, I do find some issues with it. Like when an Errata's come out - My repository is not updated until the next month. Which in turn I can miss out on patches which should or need to be installed and unless I'm on the mailing lists, I'll miss it. I have heard you can clone a channel and use that as a baseline and use the regular channel to keep everything updated. So my question is, how does everyone else do this and do I have the correct approach to clone the channel and use that as my baseline for the patching and if need be, put the servers in the main group for any errata's that come up. I would love to hear everyone thoughts on this. Thanks! Glen Collins _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><o:p></o:p> </div> <o:p> </o:p> </div> </div> </body> </html>