ports/65276: net/ntop startup script (ntop.sh) broken

[Douglas K. Rand]

>Number:         65276
>Category:       ports
>Synopsis:       net/ntop startup script (ntop.sh) broken
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 06 19:20:20 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Douglas K. Rand
>Release:        FreeBSD 4.9-RELEASE i386
>Organization:
Meridian Environmental Technology, Inc.
>Environment:
System: FreeBSD snoopy.meridian-enviro.com 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon Nov 3 21:39:37 CST 2003 rand at snoopy.meridian-enviro.com:/usr/obj/usr/src/sys/SNOOPY i386


>Description:
	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.
	
>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.
>Fix:

	Don't specify the -4 option on the ntop command line.


>Release-Note:
>Audit-Trail:
>Unformatted: