First off, if you reply to a digested message, CHANGE THE SUBJECT BACK, so that the threads stay usable and searchable for everyone else.
There are tons of fixes post 2.2c in the cvs. I'm going to roll to 3.0pre1 this weekend (unless something big comes up), so either use the cvs or wait until I post files @ SourceForge. The instructions for getting into the cvs work fine - I use them all the time. The only thing I can think of is that some client versions don't like the port #. instead of export CVSROOT=:pserver:[EMAIL PROTECTED]:2401/export/home/ntop try CVSROOT=:pserver:[EMAIL PROTECTED]:/export/home/ntop Otherwise, you'll need to post the actual problem lines from accessing the cvs. -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of Mueller, Rex > Sent: Friday, February 13, 2004 8:12 AM > To: [EMAIL PROTECTED] > Subject: [Ntop-dev] RE: Ntop-dev digest, Vol 1 #924 - 1 msg > > > Ok.. I'm 2.2c > I've tried getting into CVS via method shown and it doesn't seem to want > to fly.. Is there a tarball???? > > > ntop v.2.2c MT [i686-pc-linux-gnu] (02/12/04 04:14:37 PM build) > Copyright 1998-2003 by Luca Deri <[EMAIL PROTECTED]>. > Get the freshest ntop from http://www.ntop.org/ _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
