Bug#458819: Re: Bug#458819: ITP: nettee -- a network tee program

2008-01-05 Thread Joel Franco
Out of curiosity, besides being a bit easier to remember/type, and not requiring the user to choose a port, what benefits over combining normal tee and netcat does it have? for example: On A: nettee -in IMAGE -next B -v 31 #full logging On B: nettee -next C /dev/hda On C:

Bug#458819: ITP: nettee -- a network tee program

2008-01-03 Thread joel . franco
Hi Peter, I had not much knownledge about the torrent protocol and then i have read about it to compare to nettee. Wikipedia: - 'BitTorrent is a peer-to-peer file sharing (P2P) communications protocol' - 'downloads can take time to rise to full speed because it may take time for

Bug#458819: ITP: nettee -- a network tee program

2008-01-02 Thread Joel Franco
Package: wnpp Severity: wishlist Owner: Joel Franco [EMAIL PROTECTED] * Package name: nettee Version : 0.1.8 Upstream Author : David Mathog [EMAIL PROTECTED] * URL : http://saf.bio.caltech.edu/nettee.html * License : GPL Programming Lang: C Description

Bug#458819: ITP: nettee -- a network tee program

2008-01-02 Thread Peter Samuelson
[Joel Franco] Description : a network tee program It can typically transfer data between N nodes at (nearly) the full bandwidth provided by the switch which connects them. It is handy for cloning nodes or moving large database files. So would that make nettee a faster bittorrent?