Kismet Wireless

Kismet Forums


Posted by:dragorn
Subject:(Yet another) Kismet on Windows Q.
Date:15:46:22 10/10/2007

> I've seen other posts with errors like "I set the piddir to '/tmp/' and it now says '/tmp/, couldn't open for writing ...'", which was usually a permissions problem. (I'm using NTFS, but I have admin rights so it probably not permissions.) In my case, setting "piddir=/tmp/" does nothing at all; the error still says "/", implying an attempted write at the root directory (which should still work ...).
> Setting it to a nonsensical value (say 'sdkchdhg') also does nothing at all (the error is stil "/ ...", and not "sdkchdhg/ ..."). The only reason I know that the config file is even being parsed is because commenting it out causes a different type of failure (the you must set piddir warning ...).
> Is that more clear, or am I just confusing things more?

I'd say you're not editing the file you think you're editing then - if changes you make aren't reflected in the runtime, you're not editing the config file kismet is reading.


Reply to this message