On Thu, Jun 23, 2016 at 02:37:00PM +0000, David L. Craig wrote:
I successfully installed CRUX 3.2 on my old Acer Aspire One netbook after researching a SEGV in klogd that was identified and fixed long ago, but still after the current release. It's really obnoxious: there's a close for ksyms in the handling of an open failure for ksyms:
How did you manage to trigger this? It seems it was patched upstream in 2008? Yet somehow it never was included in the upstream release of 1.5.1? http://git.infodrom.org/?p=infodrom/sysklogd;a=commitdiff;h=74d15498a0d67552...
diff -C 1 sysklogd.original/src/sysklogd-1.5.1/ksym_mod.c sysklogd.new/src/sysklogd-1.5.1/ksym_mod.c *** sysklogd.original/src/sysklogd-1.5.1/ksym_mod.c 2014-10-04 19:47:18.000000000 +0000 --- sysklogd.new/src/sysklogd-1.5.1/ksym_mod.c 2016-06-14 22:22:59.367276801 +0000 *************** *** 191,193 **** ! fclose(ksyms); --- 191,193 ---- ! /* fclose(ksyms); dlc 2016-06-14 defanged per Debian 437213 */
This really needs to be in 3.3 (which will probably predate sysklogd-1.5.2) but in the meantime everyone can guess this is the solution to any similar symptoms they might experience. -- <not cent from sell> May the LORD God bless you exceedingly abundantly!
Dave_Craig______________________________________________ "So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe." __--from_Nightfall_by_Asimov/Silverberg_________________
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Fredrik Rinnestam