Re: pflogd: Failed to initialize: /dev/bpf0

2006-11-24 Thread Uwe Dippel
On Wed, 22 Nov 2006 22:19:37 +0200, Berk D. Demir wrote: > This permission problem smells like a mixed kernel and userland match > or a version spaghetti to me. > > Please try a recent snapshot if possible. In case you want to run > -stable, make a _clean_ build. Sounds reasonable. Only, I did

Re: pflogd: Failed to initialize: /dev/bpf0

2006-11-22 Thread Berk D. Demir
Joachim Schipper wrote: On Sun, Nov 19, 2006 at 10:11:36AM +0800, Uwe Dippel wrote: On Sat, 18 Nov 2006 21:07:57 +0100, Joachim Schipper wrote: No clue, but upgrading is a good idea and this is what it looks like on my box: [...] It doesn't look different on mine ... and the upgrade will ha

Re: pflogd: Failed to initialize: /dev/bpf0

2006-11-22 Thread Joachim Schipper
On Sun, Nov 19, 2006 at 10:11:36AM +0800, Uwe Dippel wrote: > On Sat, 18 Nov 2006 21:07:57 +0100, Joachim Schipper wrote: > > > No clue, but upgrading is a good idea and this is what it looks like on > > my box: > > [...] > > It doesn't look different on mine ... and the upgrade will happen > ho

Re: pflogd: Failed to initialize: /dev/bpf0

2006-11-19 Thread Joel Knight
--- Quoting Uwe Dippel on 2006/11/19 at 10:11 +0800: > On Sat, 18 Nov 2006 21:07:57 +0100, Joachim Schipper wrote: > > > On second thought, are you certain pflogd *should* be listening on bpf0? > > No; but it never did before (despite of the reboots) and I didn't make it > to do so. pflogd uses

Re: pflogd: Failed to initialize: /dev/bpf0

2006-11-18 Thread Uwe Dippel
On Sat, 18 Nov 2006 21:07:57 +0100, Joachim Schipper wrote: > No clue, but upgrading is a good idea and this is what it looks like on > my box: [...] It doesn't look different on mine ... and the upgrade will happen hopefully soon ... > On second thought, are you certain pflogd *should* be list

Re: pflogd: Failed to initialize: /dev/bpf0

2006-11-18 Thread Joachim Schipper
On Sat, Nov 18, 2006 at 05:41:51PM +0800, Uwe Dippel wrote: > In all of Google I found just one of these; on FreeBSD. > This machine - rebooted several times in the last 18 months - had never > had this (in /var/log/messages) before; and no changes being done to the > software, permissions or the m