<p dir="ltr">HI,<br>
I&#39;m on holiday now , but will prepare all kinds of rpms next week. <br>
Bye,<br>
CzP </p>
<div class="gmail_extra"><br><div class="gmail_quote">On Aug 19, 2016 1:57 PM, &quot;Jonathan Kaufman&quot; &lt;<a href="mailto:jkaufman@footlocker.com">jkaufman@footlocker.com</a>&gt; wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font size="2" face="sans-serif">I would like to continue to see RHEL 6
support.</font>
<br>
<br><font size="2" face="sans-serif">While ancient,  RedHat continues
to support RHEL6, and will do so as part of their OS support (which you
pay for) for 10 years.  If you opt for Extended support you can get
patches even farther out..</font>
<br>
<br><font size="2" face="sans-serif">I&#39;d think if you want to target/support
Enterprise customers,  making packages available during entirety of
the product support lifecycle  from the vendor would be ideal.</font>
<br>
<br><a href="https://access.redhat.com/support/policy/updates/errata" target="_blank"><font size="2" color="blue" face="sans-serif">https://access.redhat.com/<wbr>support/policy/updates/errata</font></a><font size="2" face="sans-serif">
(hopefully this link is available to non-customers)</font>
<br>
<br><font size="2" face="sans-serif">If the previous link isn&#39;t available
to non-customers, try this one: </font><a href="https://linuxlifecycle.com/" target="_blank"><font size="2" color="blue" face="sans-serif">https://linuxlifecycle.com/</font></a>
<br>
<br><font size="2" face="sans-serif">For RHEL 6 the current Production 2
lifecycle ends in 2017, with Production 3 support ending in 2020. </font>
<br>
<br><font size="2" face="sans-serif">I believe Centos continues to get upstream
patches during those 10 years as well.</font>
<br>
<br><font size="2" face="sans-serif">Hope this helps.</font>
<br>
<br><font size="2" face="sans-serif"><br>
Jonathan Kaufman | DevOps Engineer | Foot Locker Inc.<br>
</font>
<br>
<br>
<br>
<br><font size="1" color="#5f5f5f" face="sans-serif">From:      
 </font><font size="1" face="sans-serif">&quot;Czanik,Péter&quot;
&lt;<a href="mailto:peter.czanik@balabit.com" target="_blank">peter.czanik@balabit.com</a>&gt;</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">To:      
 </font><font size="1" face="sans-serif">&quot;Syslog-ng users&#39;
and developers&#39; mailing list&quot; &lt;<a href="mailto:syslog-ng@lists.balabit.hu" target="_blank">syslog-ng@lists.balabit.hu</a>&gt;</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Date:      
 </font><font size="1" face="sans-serif">08/01/2016 04:00 AM</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Subject:    
   </font><font size="1" face="sans-serif">[syslog-ng]
3.8 RHEL 6 packaging</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Sent by:    
   </font><font size="1" face="sans-serif"><a href="mailto:syslog-ng-bounces@lists.balabit.hu" target="_blank">syslog-ng-bounces@lists.<wbr>balabit.hu</a></font>
<br>
<hr noshade>
<br>
<br>
<br><font size="3">Hi,<br>
</font>
<br><font size="3">I think, that RHEL / CentOS 6 is ancient, but still I
ask: is there anyone who needs syslog-ng 3.8 packaged for this old Linux
release?<br>
</font>
<br><font size="3">Bye,</font>
<br>
<br><font size="3">Peter Czanik (CzP) &lt;</font><a href="mailto:peter.czanik@balabit.com" target="_blank"><font size="3" color="blue"><u>peter.czanik@balabit.com</u></font></a><font size="3">&gt;<br>
Balabit / syslog-ng upstream</font><font size="3" color="blue"><u><br>
</u></font><a href="http://czanik.blogs.balabit.com/" target="_blank"><font size="3" color="blue"><u>http://czanik.blogs.balabit.<wbr>com/</u></font></a><font size="3" color="blue"><u><br>
</u></font><a href="https://twitter.com/PCzanik" target="_blank"><font size="3" color="blue"><u>https://twitter.com/PCzanik</u></font></a><tt><font size="2">___<wbr>______________________________<wbr>______________________________<wbr>_______________<br>
Member info: </font></tt><a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank"><tt><font size="2">https://lists.balabit.hu/<wbr>mailman/listinfo/syslog-ng</font></tt></a><tt><font size="2"><br>
Documentation: </font></tt><a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank"><tt><font size="2">http://www.balabit.com/<wbr>support/documentation/?<wbr>product=syslog-ng</font></tt></a><tt><font size="2"><br>
FAQ: </font></tt><a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank"><tt><font size="2">http://www.balabit.com/wiki/<wbr>syslog-ng-faq</font></tt></a><tt><font size="2"><br>
<br>
</font></tt>
<br>
<br><br>______________________________<wbr>______________________________<wbr>__________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" rel="noreferrer" target="_blank">https://lists.balabit.hu/<wbr>mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" rel="noreferrer" target="_blank">http://www.balabit.com/<wbr>support/documentation/?<wbr>product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" target="_blank">http://www.balabit.com/wiki/<wbr>syslog-ng-faq</a><br>
<br>
<br></blockquote></div></div>