Date: Tue, 25 May 2004 22:15:05 -0400 From: Fish <fish@fish-mail.com> To: freebsd-mobile@freebsd.org Cc: Michael Cheselka <ryoohki@ryoohki.org> Subject: Re: DWL-650 & Kismet Message-ID: <200405252215.05346.fish@fish-mail.com> In-Reply-To: <40B3C33A.6040706@ryoohki.org> References: <200405200904.37966.fish@fish-mail.com> <20040525203957.GC5559@moya.lambermont.dyndns.org> <40B3C33A.6040706@ryoohki.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 25 May 2004 06:05 pm, Michael Cheselka wrote: > Hans Lambermont wrote: > >Here's my top kismet part: > > > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > >13391 root 76 0 2776K 2140K select 0:06 2.34% 2.34% > > kismet_server 13389 hans 76 0 2980K 2416K select 0:00 0.00% > > 0.00% kismet_server 13393 hans 76 0 3104K 2484K select 0:00 > > 0.00% 0.00% kismet_client 13394 hans 76 0 2904K 2224K select > > 0:00 0.00% 0.00% kismet_client and some more clients. > > Why two kismet_server processes? Why so many kismet_client process > table entries? > > Thanks! > Mike One is the regular kismet_server, the other does channel control. I got this when I started kismet_server and then killed the lower-number process... Sending termination request to channel control child 29490... Waiting for channel control child 29490 to exit... I'm not sure about the clients, but that explains the servers. FYI, I have the same problem on my side. Kismet takes as much processor as it can, and never picks up any access points. Hope this helps someone. Fish
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405252215.05346.fish>