| Summary: | kismet init script problems | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Justin <justin> |
| Component: | Current packages | Assignee: | Peter Johanson (RETIRED) <latexer> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Justin
2003-02-03 16:33:26 UTC
New tarball w/ initscripts should be propogating soon. Kismet server will _not_ start from the init script if you do not set a full path to a writeable directory for the logtemplate setting in /etc/kismet/kismet.conf e.g. suiduser=foo logtemplate=/home/foo/kismet/%n-%d-%i.%l Soon as i have a card to test the wlan-ng drivers w/ (coming in the mail tomorrow), i'll fix the script to work w/ wlan-ng stuff to. Until then, comment out the three lines in /etc/init.d/kismet This bug is more than 180 days old. I'm resolving as TEST-REQUEST. Please reopen if the problem persists. |