LinuxQuestions.org - weird iptraf issue....

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - weird iptraf issue.... (https://www.linuxquestions.org/questions/slackware-14/weird-iptraf-issue-526380/)

weird iptraf issue....

We had a blackout the other day and unfortunately I wasn't around to shut down my Slack server correctly. The data line of the UPS is running to the other computer unfortunately. So my server took a hard nose dive I guess you can say.

And as the title says the only issue I have since the shutdown is a weird problem with iptraf. Before my server went down I had a couple instances of iptraf running which monitored the network traffic obviously. I set each instance to record different data and log it. Now, after I restarted the machine and try to open some new instances of iptraf it tells me that some instances are still running...OR if I am configuring it, it tells me only the first instance can configure it. Problem is of course, that it wasn't running before I started it up again. So it's like it's running in the background and I don't notice it (top doesn't show it). The ghost of iptraf or something. So are there any suggestions out there on how to fully kill the process? I tried reinstalling just iptraf but it still does it. Any ideas?

From http://cebu.mozcom.com/riker/iptraf/2.7/cmdline.html:

Quote:

-f

Forces IPTraf to clear all lock files and reset all instance counters to zero before running any facilities. IPTraf will then think it's the first instance of itself.

The -f parameter overrides the existing locks and counters imposed by the IPTraf process and by the various facilities, causing this instance to think it is the first and that there are no other facilities running. Use this parameter with great caution. A common use for this parameter is to recover from abrupt or abnormal terminations which may leave stale locks and counters still lying around.

Hope that helps,
- Piete.

That fixed it. Thanks. :)