Re: Release of Version 2.2.1
Hi, It's been a while since Version 2.2 was released, so it's time for the next release. I'd like to fix the reported memory leak issue, and then release it later next week. The changes are minor, and mostly cleanups and bug fixes. Please let me know if there are any issues. According to current GIT in 2.x.x, my patch to prevent SIGTERM turning into SIGSEGV is not included yet. A proper shutdown is required on all systems using systemd, so I believe it would be very useful to get this into the mainstream release. For the mini, two-line patch which prevents this (admittedly not totally clean), please see my message to -devel on 12 Oct 2012, titled SIGTERM - SIGSEGV. Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 signature.asc Description: OpenPGP digital signature - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Release of Version 2.2.1
Stefan Winter wrote: According to current GIT in 2.x.x, my patch to prevent SIGTERM turning into SIGSEGV is not included yet. I think we have a better solution. :) For the mini, two-line patch which prevents this (admittedly not totally clean), please see my message to -devel on 12 Oct 2012, titled SIGTERM - SIGSEGV. I've added the patch to set rcode=1 on clean exit. The patch to remove free_mainconfig() is made unnecessary by other cleanups. The SEGV was a result of mis-ordered free's. There was conflict between the modules free'ing their data, and the main configuration code free'ing its data. That was fixed. The code was run through valgrind repeatedly until it shows no errors on exit. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Release of Version 2.2.1
On 03/07/2013 12:22 PM, Alan DeKok wrote: It's been a while since Version 2.2 was released, so it's time for the next release. I'd like to fix the reported memory leak issue, and then release it later next week. The changes are minor, and mostly cleanups and bug fixes. Please let me know if there are any issues. Yes, one just came up. We've never been able to ship a devel package that installs the header files because of multilib conflicts. A multilib conflict occurs when arch specific packages (i.e. i686 vs. x86-64) contain arch independent files which differ between arches (i.e. header files). In other words the header files can't differ between i686 and x86-64. My recollection is there was just one or two issues that arose because configure generates a header file with a few defines specifying the size of an int or some such. This wiki page explains some of the issues. http://fedoraproject.org/wiki/PackagingDrafts/MultilibTricks Anyway, I just got a request to start shipping a -devel package, but it's much easier to make the necessary minor tweaks upstream to get rid of the conflicts. So it would be great if we could get this into the git repo before 2.2.1 goes out the door. I think the fix is fairly minor. Since this just came up about 5 minutes ago I don't have all the details at hand or a patch yet, but I'll do that soon. -- John Dennis jden...@redhat.com Looking to carve out IT costs? www.redhat.com/carveoutcosts/ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Release of Version 2.2.1
John Dennis wrote: Yes, one just came up. We've never been able to ship a devel package that installs the header files because of multilib conflicts. A multilib conflict occurs when arch specific packages (i.e. i686 vs. x86-64) contain arch independent files which differ between arches (i.e. header files). In other words the header files can't differ between i686 and x86-64. Hmm... OK. My recollection is there was just one or two issues that arose because configure generates a header file with a few defines specifying the size of an int or some such. This wiki page explains some of the issues. I'll take a look. Anyway, I just got a request to start shipping a -devel package, but it's much easier to make the necessary minor tweaks upstream to get rid of the conflicts. So it would be great if we could get this into the git repo before 2.2.1 goes out the door. I think the fix is fairly minor. It may be possible. Arran did a bunch of fixes for 3.0, so that the installed header files now have *none* of the HAVE_* stuff. That makes it much easier to create development headers. I'm not sure how easy this is for 2.2. I'd prefer to keep that code as stable as possible. Since this just came up about 5 minutes ago I don't have all the details at hand or a patch yet, but I'll do that soon. Thanks. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Release of Version 2.2.1
Arran did a bunch of fixes for 3.0, so that the installed header files now have *none* of the HAVE_* stuff. That makes it much easier to create development headers. Yes people who include autoconf generated headers in public headers need beating with sticks. -Arran - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Release of Version 2.2.1
It's been a while since Version 2.2 was released, so it's time for the next release. I'd like to fix the reported memory leak issue, and then release it later next week. The changes are minor, and mostly cleanups and bug fixes. Please let me know if there are any issues. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
