Copied to dapper-updates, thank you!
** Changed in: nis (Ubuntu Dapper)
Status: Fix Committed => Fix Released
--
/usr/lib/yp/ypxfr produces segmentation fault
https://bugs.launchpad.net/bugs/47815
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direc
I was able to successfully reproduce the issue using the dapper amd64
version of nis 3.15-3ubuntu2 in a slave configuration against an i386
hardy NIS master server. After upgrading the version of nis on the
dapper slave to the version in dapper-proposed, 3.15-3ubuntu3, I can
confirm that that the y
Steve, thank you for testing! BTW, since this is so old already, I'm
actually more concerned about a test which shows that the package
still by and large works. If the bug is not reproducible, we shouldn't
waste too much time trying to reproduce it.
If the bug is not fully fixed, we can always do
Ah, thanks, that's the problem, I was testing from a hardy amd64 NIS
master server. I'll try to reproduce again from an i386 master. Thanks!
--
/usr/lib/yp/ypxfr produces segmentation fault
https://bugs.launchpad.net/bugs/47815
You received this bug notification because you are a member of Ubuntu
What architecture is the NIS server? The NIS server must be a Linux
server running on an incompatible architecture (eg, i386).
The problem is that NIS attempts to transfer the map by copying the
architecture dependant database file verbatim rather than transferring
the keys individually. It may be
I've spent a fair amount of time attempting to reproduce this bug on an
am64 dapper instance, unfortunately with no success. I am able to ypxfr
maps with the YP_SECURE key set on it from a hardy nis server to both
the originally shipped version of nis (3.15-3ubuntu2) and the version in
dapper-propo
Unfortunately I can't provide testing for dapper at present - none of
the AMD64 systems I have appear able to boot it these days. :(
--
/usr/lib/yp/ypxfr produces segmentation fault
https://bugs.launchpad.net/bugs/47815
You received this bug notification because you are a member of Ubuntu
Bugs, w
Thanks for the confirmation. Closing the hardy task.
** Changed in: nis (Ubuntu)
Status: Incomplete => Fix Released
--
/usr/lib/yp/ypxfr produces segmentation fault
https://bugs.launchpad.net/bugs/47815
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
It's only an issue in dapper - it was a bug in the compiler which was
resolved before feisty.
Will try to test this weekend.
--
/usr/lib/yp/ypxfr produces segmentation fault
https://bugs.launchpad.net/bugs/47815
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I uploaded your patch to dapper-proposed, please test.
Also, is this still an issue in Gutsy and hardy? We need to fix it in
Hardy first before this can go to any -updates.
** Tags added: verification-needed
** Changed in: nis (Ubuntu Dapper)
Status: Confirmed => Fix Committed
** Changed
I've reproduced the problem on dapper.
** Description changed:
+ Due to a compiler misoptimisation on amd64 in dapper ypxfr crashes when
+ attempting to bulk transfer maps. This means that as standard the
+ package can't be used to provide a slave server when the master can do
+ bulk transfers. T
No SRU request here, unsub'ing ubuntu-sru.
--
/usr/lib/yp/ypxfr produces segmentation fault
https://bugs.launchpad.net/bugs/47815
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
Seems like a sensible state given that Ubuntu doesn't use bzr for this.
** Changed in: nis (Ubuntu)
Status: In Progress => Fix Committed
--
/usr/lib/yp/ypxfr produces segmentation fault
https://bugs.launchpad.net/bugs/47815
You received this bug notification because you are a member of Ub
I'm not sufficiently familiar with how this stuff is handled to know
what to do with this now.
** Changed in: nis (Ubuntu)
Status: Confirmed => In Progress
--
/usr/lib/yp/ypxfr produces segmentation fault
https://launchpad.net/bugs/47815
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
This patch works around the problem in a non-invasive fashion - I wasn't
able to come up with a code based workaround. None of the unoptimised
code should be particularly performance critical.
** Attachment added: "Build ypxfr without optimisation"
http://librarian.launchpad.net/6847430/nis-opt
** Changed in: nis (Ubuntu)
Assignee: (unassigned) => Mark Brown
--
/usr/lib/yp/ypxfr produces segmentation fault
https://launchpad.net/bugs/47815
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Actually, this may well be Ubuntu-specific: it looks like a compiler
bug. xdr_ypresp_val() should be passing the xdrs it was given into
xdr_valdat() but as can be seen from the backtrace it isn't. It looks
rather like the first argument has been dropped and the remaining
arguments are being passed
I've reproduced this on dapper. ypxfr crashes on amd64 if there is a
YP_SECURE key in the map (so mostly only for shadow maps).
Backtrace:
#0 0x2ae47c05 in free () from /lib/libc.so.6
#1 0x2aecb9a8 in xdr_bytes_internal () from /lib/libc.so.6
#2 0x004033b8 in xdr_valdat
Got:
Transferring passwd.byuid...
Transferring ypservers...
Transferring passwd.byname...
Transferring shadow.byname...
/usr/lib/yp/ypinit: line 37: 27831 Segmentation fault $YPBINDIR/ypxfr -f
-h $MASTER -c -d $DOMAIN $map
YPINIT: WARNING: Couldn't exec /usr/lib/yp/ypxfr -f -h -c -d
shadow
19 matches
Mail list logo
