<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to patches</title><link>https://sourceforge.net/p/dnx/patches/</link><description>Recent changes to patches</description><atom:link href="https://sourceforge.net/p/dnx/patches/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 14 Aug 2008 16:02:04 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/dnx/patches/feed.rss" rel="self" type="application/rss+xml"/><item><title>HOST_NAME_MAX undefined on some systems</title><link>https://sourceforge.net/p/dnx/patches/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hey there,&lt;/p&gt;
&lt;p&gt;I’m packaging DNX for Fedora based on John Calcote’s OpenSUSE specfile, and I ran across the following issue:&lt;/p&gt;
&lt;p&gt;DNX relies on the HOST_NAME_MAX macro in common/dnxTcp.h and common/dnxUdp.h. This constant is not guaranteed to work on POSIX systems, and leads to build problems in several versions of Fedora and elsewhere. Instead, sysconf(_SC_HOST_NAME_MAX) should be used at runtime to retrieve the value from the running kernel. I've also added support for MAXHOSTNAMELEN on older Solaris, and fall back to a sensible default (255) on other platforms.&lt;/p&gt;
&lt;p&gt;This is defined as a new int, max_hostname, in common/dnxProtocol.c. Changes were made to common/dnxTcp.c and common/dnxUdp.c to make them only error out if the length is greater than 0, as -1 indicates the system does not have a maximum hostname size.&lt;/p&gt;
&lt;p&gt;See attached patch.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 14 Aug 2008 16:02:04 -0000</pubDate><guid>https://sourceforge.net1b20127229fced83d4f4f452be647667e1ce7dbe</guid></item><item><title>patch for nagios-2.10</title><link>https://sourceforge.net/p/dnx/patches/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I've not tested this much yet so far but I've modified the existing patch to apply against 2.10&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Graham</dc:creator><pubDate>Thu, 22 Nov 2007 17:30:17 -0000</pubDate><guid>https://sourceforge.net84882fe7c98579219a917fc2f238ff670172cd77</guid></item></channel></rss>