Bug 65276 - net/ntop startup script (ntop.sh) broken
Summary: net/ntop startup script (ntop.sh) broken
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Clement Laforet
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-07 03:20 UTC by rand
Modified: 2004-04-07 14:56 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rand 2004-04-07 03:20:20 UTC 
	The -4 argument to ntop in the ntop.sh startup script is undocumented
	and eats the following --set-pcap-nonblocking option, which breaks
	ntop when the -d switch is provided.

Fix: 

Don't specify the -4 option on the ntop command line.
How-To-Repeat: 	The command line
		/usr/local/bin/ntop -d -L --set-pcap-nonblocking -i xl0 -w 3000 -W 0 -u nobody
	works but the command line
		/usr/local/bin/ntop -d -L -4 --set-pcap-nonblocking -i xl0 -w 3000 -W 0 -u nobody
	doesn't. The problem is that all requests of ntop's web server simply
	block. This was reported at http://www.mail-archive.com/ntop-dev@unipi.it/msg03153.html
	The undocumented -4 (--ipv4) option expects an argument, and eats the
	--set-pcap-nonblocking argument. By dropping the -4 everything works.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2004-04-07 06:12:18 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->clement

Over to maintainer.
Comment 2 Clement Laforet freebsd_committer freebsd_triage 2004-04-07 14:55:57 UTC 
State Changed
From-To: open->closed

Fix committed. Thanks for your report!