Date: Sat, 15 Oct 2016 17:35:13 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 213506] YP/NIS: yppush, ypxfr dump core Message-ID: <bug-213506-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213506 Bug ID: 213506 Summary: YP/NIS: yppush, ypxfr dump core Product: Base System Version: 11.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: la5lbtyi@aon.at I have a YP (NIS) setup with one master server and several slave servers. O= ne of the latter is in ypservers (together with the master server, as setup by ypinit -m). If I modify a YP-relevant file on the master server and do a 'make' in /var= /yp, yppush fails with a segmentation violation (signal 11) and dumps core. This aborts 'make', thereby not processing the remaining maps. If I manually ypxfr a map from the master to any of the slave servers (invo= ked at the respective slave server as "ypxfr -h <master server> <map name>"), y= pxfr fails with a segmentation violation (signal 11) and dumps core. It leaves a zero-sized file in /var/yp/<domainname> with a .nnnn suffix, e.g., rpc.byname.4631. None of this happened with 10.3. Btw, the only maps which can be successfully transferred are empty ones, i.= e., containing no entries. The associated file in /var/yp/<domainname> has a si= ze of 40960 bytes. One more note: this started to happen several months ago on 11-current comp= iled for armv6. At that time I thought it was just a problem on that architectur= e. But now, after installing 11.0 on all my machines, it happens on all of them (amd64 and i386). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213506-8>