Issue #2728 has been updated by ftigeot.
sudo-1.8.11.p1 is working fine on FreeBSD -current, this may still be a
DragonFly bug.
Bug #2728: Sudo doesn't reap it's children
http://bugs.dragonflybsd.org/issues/2728#change-12237
* Author: zcrownover
*
Issue #2728 has been updated by zcrownover.
I forgot to mention it, but for clarity sake, the file I attached earlier is a
ktrace file.
Bug #2728: Sudo doesn't reap it's children
http://bugs.dragonflybsd.org/issues/2728#change-12238
* Author:
Issue #2729 has been reported by lhmwzy.
Bug #2729: DragonFly_RELEASE_4_0 make buildkernel error
http://bugs.dragonflybsd.org/issues/2729
* Author: lhmwzy
* Status: New
* Priority: Normal
* Assignee:
* Category:
* Target version:
Issue #2729 has been updated by lhmwzy.
the kernel config:
platformpc64
machine x86_64
machine_archx86_64
cpu HAMMER_CPU
ident lhmwzy
maxusers0
#optionsCPU_DISABLE_AVX
options INET#InterNETworking
options
Issue #2729 has been updated by lhmwzy.
make a patch and solved it.
please review it.
--- sys/net/pf/pf_table.c.orig 2014-11-05 12:37:46.563579000 +0800
+++ sys/net/pf/pf_table.c 2014-11-05 12:26:31.879782000 +0800
@@ -1976,7 +1976,9 @@
struct pfr_kentry *ke = NULL;
Issue #2728 has been updated by dragonflybsd1.
joris mentions the patch provided in that ticket worked.
What happens with that patch? pushed to freebsd ports? Are they not affected
by the issue -- truly? why not?
Bug #2728: Sudo doesn't reap it's
Issue #2719 has been updated by dragonflybsd1.
Please report dports issues like this to:
https://github.com/DragonFlyBSD/DPorts/issues
That being said, this looks like an issue at the freebsd ports level. E.g. you
need to file a PR here instead:
Issue #2727 has been updated by dragonflybsd1.
Status changed from New to Closed
problem resolved by now.
Bug #2727: Installation Error of Latest snapshot
http://bugs.dragonflybsd.org/issues/2727#change-12245
* Author: fahadpv
* Status: Closed
*
