Around the time of your original message there were mail server problems - many users submissions got blocked. IIRC Pisa blocked every ISP who had ever had any user send spam to them. I know they blocked AT&T and a bunch of other big ones. And they blocked based on the originating IP address, so any customer of those ISPs, regardless of which mail server they used was blocked. After the problems were fixed, I resent the ~80 messages that were lost - hence the lag.
There are a couple of FreeBSD users I know of - Stanley Hopcroft in OZ is running 4.7, Rob Trout has a couple of boxes. Tony Nelson has provided me shell access in the past. Let's see... Mustafa Baig responded to the first message in this chain about .deps. Others who've emailed the list WRT FreeBSD the last two months include Tim Gardner, Jean Hernandez, Mark Cole (runs 3.5.1 -- poor SOB), and Alvaro Pietrobono. I built piglet, a FreeBSD4.7 box this weekend for testing on this problem. I'm going to move that to 5.0 next. I run FreeBSD 4.6.3 on Tigger as one of the 6 OSes I use for ntop development - and FreeBSD is the only one I regularly test under. I've just committed a trap for the .deps problem and added docs/FAQ entries for it. But realistically, it's a FreeBSD port problem - they're still distributing the 1.5 version of automake, which was released a long, long, time ago. Index of ftp.gnu.org/gnu/automake (lightly edited): automake-1.5.tar.gz 515 KB 2001-08-23 02:50:28 PM automake-1.6.tar.gz 575 KB 2002-03-06 03:30:48 PM automake-1.6.1.tar.gz 582 KB 2002-04-11 09:42:08 AM automake-1.6.2.tar.gz 593 KB 2002-06-14 08:07:53 AM automake-1.6.3.tar.gz 596 KB 2002-07-28 06:46:43 PM automake-1.7.tar.gz 642 KB 2002-09-25 10:19:42 PM automake-1.7.1.tar.gz 648 KB 2002-10-19 04:09:02 AM automake-1.7.2.tar.gz 662 KB 2002-12-05 10:37:55 PM I realize that there are issues with auto* tool versions - check the back traffic for some of my rants about them, especially the incompatibilities 'tween 1.6 and 1.7 (or 1.4 and 1.5 or 1.5 and 1.6 for that matter). Still, the problem is not ntop's - we clearly indicate our dependency on 1.6. If people bothered to READ the output from ./configure, the error message that occurs during the depcomp copy is clearly in there -- even without the trap I just put. With the trap, well, ./configure will stop and they can't ignore it. As to why there aren't a lot of posts? My guesses 1) People are happy with the old version of ntop in the FreeBSD ports. Which, BTW is ntop-2.0.99-rc2.tgz, i.e. a release candidate for ntop 2.1 - they really should be updated to 2.1.3 for a LOT of reasons. or 2) Since the problem was only exposed if you executed automake and that happened only if you didn't have depcomp, I'm guessing that they just keep reusing the same directory. If you download and untar into the same directory (e.g. ntop-current), then it updates the various files (giving you the 1.6.3 generated files) and since you already depcomp, it doesn't remake them... so no .deps problem! -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of E. Farah Sent: Monday, January 20, 2003 9:35 AM To: [EMAIL PROTECTED] Subject: [Ntop] FreeBSD (et al) and the .deps problem Burton, This is the sort of thing that I was hoping not to get into. No I am not owed an answer, and I know this is a free list. I was just hoping to intiate an interesting discussion around Ntop that would benefit other users, not just myself. Thanks for your reply regarding TCPUDMP, I did not see it since it was sent 2 weeks after I post it. I know a lot of FreeBSD users run Ntop. I am surprised there's not too many post around it. I am only receiving the daily digests now that's why I don't have the original message, but I will change that. _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
