http://bugzilla.novell.com/show_bug.cgi?id=578934 http://bugzilla.novell.com/show_bug.cgi?id=578934#c2 Steve Revilak <steve@srevilak.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|steve@srevilak.net | --- Comment #2 from Steve Revilak <steve@srevilak.net> 2010-02-17 02:05:04 UTC --- Uwe, Thanks for looking at this. After seeing the segfault, my first instinct was to check for upgraded packages (i.e. "zypper update"). I allowed zypper to upgrade all of the packages it identified, then rebooted the machine. After reboot, the segmentation fault in isc_file_isabsolute was still consistently reproducible. I reinstalled OpenSUSE over the weekend. (I decided that I wanted to partition the disks differently. Since my initial installation was only a few days prior, a clean install seemed easiest.) After re-installing, named no longer segfaults on startup; named works perfectly well now. I had made notes during my first installation. With the exception of disk partitioning, I tried to follow the same procedure during my second installation. (In both cases, / was RAID 1, using mdadm.) Unfortunately, I don't know why the segfaults occurred in my first installation, but not the second. If the segmentation faults occur again, I will try disabling AppArmor as you suggested. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.