1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
This is the beginning of a FAQ for IPTraf.
---
Q: Could you include support for <this-and-that> interface?
A: Please read the README.interfaces file for what is needed for a new
interface type to be supported.
Q: I try to start IPTraf but it tells me that <facility> is already active
in another process. But I'm sure IPTraf isn't running at the time!
A: Probably due to a faulty installation. However if you're sure you've
installed the software properly, you may have stale lock files from a
previous abort. Just issue the iptraf command with the -f parameter.
This will override stale locks and IPTraf should proceed normally.
Q: I want to configure IPTraf but it tells me only the first instance can
configure.
A: Similar to the previous question. Issue the iptraf command with the -f
parameter.
Q: Is there a way to make IPTraf run in the background and collect
statistics to a log file?
A: Prior to 2.1.0, there was no elegant way of doing so. Version 2.1.0
and later have the -B command-line parameter to force IPTraf to dump all
its screen output into oblivion and move into the background. See the
manual for details on background operation.
Q: I get the error message "Unable to open raw socket".
A: If you're using IPTraf 2.x, you must be running version 2.0.x of the
Linux kernel. Furthermore, the "Packet Socket" driver must be installed.
Most stock kernels include this driver already. Be sure to include it if
you're compiling a custom kernel.
Q: I'm getting a "cannot allocate memory" error but I've got loads of
memory available.
A: The "cannot allocate memory" error is a reponse to the "segmentation
fault" condition (SIGSEGV). If you're sure it's not a memory condition on
your machine, please report it to me, and if possible, include a gdb trace
or strace output to help me debug.
|
