No... run grep on the source - you'll find where the database names are set and the fields that make them up.
But I still think it's a gdbm problem. Have you tried DELETING all of the .db files and recreating the password... -----Burton -----Original Message----- From: Stieglitz, Eric J. (DCSA) [mailto:EStieglitz@;exchange.ml.com] Sent: Wednesday, October 23, 2002 1:45 PM To: 'Burton M. Strauss III'; Ntop Cc: Johnston, Christopher (DCSA) Subject: RE: [Ntop] command vs. daemon mode I want to make sure I understand -- you want me to run a `strings -a` on the ntop binary and grep for '\.db' ? I'll need to check the allocated size thing by checking Solaris 8 specs... GDBM is an interesting idea. I'll have to look at that. /EJS -----Original Message----- From: Burton M. Strauss III [mailto:Burton@;ntopsupport.com] Sent: Wednesday, October 23, 2002 1:59 PM To: Ntop Cc: Stieglitz, Eric J. (DCSA) Subject: RE: [Ntop] command vs. daemon mode grep for '\.db' -- you'll see the snprintf()s that make the char[] value for the open()s. I think you're right about where it's writing to... What strikes me as odd is the uniform size, unless Solaris is showing allocated size? 11:37:45 tigger [Linux] user=bstrauss pwd=/shared/work/linux/ntop $ ls /usr/share/ntop -l *.db total 7344 -rw-r--r-- 1 root root 12361 Oct 23 12:02 addressCache.db -rw-r--r-- 1 root root 18931 Oct 23 12:09 dnsCache.db -rw-r--r-- 1 root root 7407857 Oct 23 12:09 hostsInfo.db -rw-rw-r-- 1 root root 12859 Oct 23 12:09 LsWatch.db -rw-r--r-- 1 root root 12437 Oct 12 17:17 ntop_pw.db -rw-r--r-- 1 root root 12775 Oct 23 10:47 prefsCache.db It's GOT to be some kind of permissions problem, but I'm completely clueless as to what. - Check out this article - http://www.systemtoolbox.com/article.php?articles_id=109 - there seem to be some Solaris tools you can use to query and write to gdbm databases.. - Have you asked on the gdbm list? -----Burton -----Original Message----- From: Stieglitz, Eric J. (DCSA) [mailto:EStieglitz@;exchange.ml.com] Sent: Wednesday, October 23, 2002 12:00 PM To: 'Burton M. Strauss III'; [EMAIL PROTECTED] Subject: RE: [Ntop] command vs. daemon mode Burton, How does one figure out where ntop is trying to write its .db files? I'm pretty sure that these are going in /usr/local/var/ntop: # ls -al /usr/local/var/ntop total 292 drwxrwxrwx 2 root root 512 Oct 23 12:55 . drwxr-xr-x 3 root root 512 Oct 23 12:43 .. -rwxrwxrwx 1 root root 24576 Oct 23 12:43 LsWatch.db -rw-r--r-- 1 root root 24576 Oct 23 12:55 addressCache.db -rwxrwxrwx 1 root root 24576 Oct 23 12:43 dnsCache.db -rwxrwxrwx 1 root root 24576 Oct 23 12:43 hostsInfo.db -rwxrwxrwx 1 root root 24576 Oct 23 12:43 ntop_pw.db -rwxrwxrwx 1 root root 24576 Oct 23 12:43 prefsCache.db Now, here's something interesting....I did a chmod a+rwx on this directory to see if that affected anything. When I restarted ntop with `ntop -u sysadmin`, obviously addressCache.db was recreated because its permissions are not the same as the other files! Any idea as to what could be causing this? _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
