On Sat, Feb 18, 2006 at 08:16:37AM +0100, Oliver J. Morais wrote:
Just added two capture-sources to the kismet.conf, no special config,
fired up kismet with sudo kismet. Everything fine, but after some
time the number of kismet_client seems to be growing and growing...
Is this
* Matthias Kilian [EMAIL PROTECTED] [060218 08:55]:
For now, try to disable the sound. It seems that kismet_client tends
to fork amok when sound is enabled.
OK, thanks for the info. I disabled the sound now, I'll report later
if that helped.
For now, try to disable the sound. It seems that kismet_client tends
to fork amok when sound is enabled.
If you set sound=true but soundplay= points to a non-existing file,
execve(2) fails (ENOENT) and the forked child does not get harvested.
I have a better fix for when (if) a new -stable is
i386, OpenBSD 3.9-beta (GENERIC) #597: Sun Feb 5 21:14:35 MST 2006
Ports from the same date, kismet built via ports.
Just added two capture-sources to the kismet.conf, no special config,
fired up kismet with sudo kismet. Everything fine, but after some
time the number of kismet_client seems to
