Bug 94205 – [net-wireless/kismet-2005.04.1] init script fails to stop.

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Manolis Tzanidakis 2005-05-27 10:40:48 UTC]

The init script for kismet has a command 'kismet_unmonitor' which is 
unavailable on my system & thus fails to set init status to stopped
although it stops kismet_server correctly.

Reproducible: Always
Steps to Reproduce:
1.configure /etc/kismet.conf
2./etc/init.d/kismet start && sleep 2 && /etc/init.d/kismet stop
3./etc/init.d/kismet status | grep stopped  

Actual Results:  
nothing returned :).

Expected Results:  
return: 
 * status:  stopped


I've built kismet without gps & ethereal support.

[Comment 1 fbusse 2005-06-10 07:28:06 UTC]

Same thing here, kismet_unmonitor is simply missing.

[Comment 2 Henrik Brix Andersen 2005-06-11 05:24:44 UTC]

It appears the kismet_unmonitor script is no longer included in the distribution
of kismet. I'll have to look into another way of stopping the server.

[Comment 3 Manolis Tzanidakis 2005-06-13 01:58:03 UTC]

AFAIK, latest versions of kismet do 'unmonitor' automatically (check upstream's
CHANGELOG). So it's not required to have such function in init script.
At least it does work ok on my ipw2100.

[Comment 4 Henrik Brix Andersen 2005-06-13 03:11:33 UTC]

Yeah, I've found out as much myself. This will be fixed in the next revbump.

[Comment 5 Henrik Brix Andersen 2005-06-13 03:40:25 UTC]

Fixed in net-wireless/kismet-2005.04.1-r1. Thank you for reporting this.