Re: [patch] DUID in fstab(5) breaks quota(1) reporting

2013-11-04 Thread Dimitri Sokolyuk
Two releases after this simple patch is still not commited and the bug is still present. Could please anyone from the core-team check and commit it? wbr, Dimitri Sokolyuk On 25 Feb 2013, at 16:38, Dimitri Sokolyuk sokol...@gmail.com wrote: Synopsis:DUID in fstab(5) breaks quota(1)

Re: [patch] DUID in fstab(5) breaks quota(1) reporting

2013-11-04 Thread Brad Smith
On 04/11/13 7:13 PM, Dimitri Sokolyuk wrote: Two releases after this simple patch is still not commited and the bug is still present. Could please anyone from the core-team check and commit it? wbr, Dimitri Sokolyuk There has been some discussion regarding fixing this issue but I believe the

Re: [patch] DUID in fstab(5) breaks quota(1) reporting

2013-11-04 Thread Dimitri Sokolyuk
I undersand. But it will be really helpful, if this bug is fixed at least as workaround, until itÂ’ll get fixed in the right manner. Right now the quota(1) tool is plain broken and useless and this still many releases (since DUID introduction). On 5 Nov 2013, at 01:16, Brad Smith b...@comstyle.com

3 Nov i386 snapshot: panic: kernel diagnostic assertion __mp_lock_held(sched_lock) == 0 failed

2013-11-04 Thread Matthew Clarke
Synopsis: panic: kernel diagnostic assertion __mp_lock_held(sched_lock) == 0 failed Category: kernel Environment: System : OpenBSD 5.4 Details : OpenBSD 5.4-current (GENERIC.MP) #117: Sun Nov 3 11:42:47 MST 2013

Re: 3 Nov i386 snapshot: panic: kernel diagnostic assertion __mp_lock_held(sched_lock) == 0 failed

2013-11-04 Thread Matthew Clarke
Mon, Nov 04, 2013 at 15:47:13 -0800, I wrote: Synopsis:panic: kernel diagnostic assertion __mp_lock_held(sched_lock) == 0 failed Category:kernel Environment: [ snip ] I copied the trace information, but there was too much in the ps listing to copy (no serial port on