I'm (still !!!!) messing about with ntop configuration ..... now its the
latest snapshot in a 4.1 RELEASE system. I've compiled gdbm /
compiled ntop (with gcc, since it doesn't like the base FreeBSD
compiler at all) ..... noticed it found SSL and incorporated that, so
at least this here beast isn't wide open to all the merryhackers
 
When I run /usr/local/bin/ntop, it returns
 
'/usr/local/var/ntop/dnsCache.db' open failed
 
OK so I figure I'll fix this sucker by creating a dnsCache.db using makemap hash
on a blank dnsCache ..... that returns
 
'/usr/local/var/ntop/dnsCache.db' open failed: Bad magic number
'Possible solution: please use '-P <directory>'
 
Well that didn't work ..... so lets make a blank /tmp/ntop directory, make it world read / write, and point ntop at that with "ntop -P /tmp/ntop"  ...... that returns
 
'/usr/local/var/ntop/dnsCache.db' open failed
 
OK so lets see now ..... looks to me like ntop can actually SEE the blank db
" /usr/local/var/ntop/dnsCache.db"  but it doesn't like what it sees so it spits
the dummy. Ah ha ...... what say we copy a "real" db file, like virtusertable.db
to dnsCache.db & see it it sees eye to eye with that. Nahhhhh no such luck ...
back to the cracked record "bad magic number" complaint :(
 
So where to from here ?? ........ anyone have suggestions ??
 
FWIW, at end of gdbm compile there was a message I didn't understand about linking something or other ....... could that be a factor ??

Reply via email to