I have found some similar problems.  I installed ntop on mac os X and have had it kernel panic a few times.  I have not found a resolution yet.  One time when i restarted I was getting a gdbm read error when I tried to re-start ntop.  I found after some research that deleteing or re-naming the files in /usr/local/ntop-3.2/var/ntop/*.db resolved my problem with gdbm.  I am on Mac OS X 10.4.2 on a mini mac. 
Thanks
Scott

On 10/30/05, Steve Abrahall <[EMAIL PROTECTED] > wrote:
Hi

I'm finding after the machine has been on for about 3 or 4 days (or a
week which is how long I usually leave it between restarts)

I often get a kernal panic if I control quit out of ntop
I also get a gdbm permissions related error (but not every time)

Anyone else finding this?

a work around is to just re install ntop after deleteing the

/usr/local/ntop-3.2/ folder

I'm currently using

Using
Mac os X 10.4.1 (am upgrading to 10.4.2 as I write this)
Ntop 3.2 via the Standard mac os X  installer

(Only thing that's a little diffrent is that I am using a 300 line
list of ports but I intend to cut this back a bit in time)

Interesting in that the machine useed to run 3.1 on an older version
of the operating system
without this sort of issue. (Although I know os X can get finikey
about Ram timimg issues)
Slimm possibility this could be ram hardware related but very slim as
the mac has been running 3.1 for about a year or so.


Any thoughts on the above greatly appreciated!

Steve




_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to