[Udpcast] Feature Requests: named sessions and no timeout messages

[Michael D. Setzer II]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In my case, I have found using the --max-bitrate=xxM as a way of greatly 
reducing this. I have one system in a lab that has a harddrive that doesn't 
keep up with the others (all same drives). Test on drive show no problems, 
but moving it from one system to another causes the error to move, so it is 
the drive. Happens when it is moving the large empty parts of the drive, 
where it has been cleared out. In this case the network is transferring more 
data than this drive can write. It will sometimes fall about 1GB behind the 
others. (1GB of Ram in systems). Using the max-bitrate reduces or 
eliminates the timeout messages, but does make the process take longer, 
since it limits the transmission when it could be writing faster.


On 26 Jun 2006 at 20:17, D G Teed wrote:

Date sent:      	Mon, 26 Jun 2006 20:17:39 -0300 (ADT)
From:           	D G Teed <dteed at artistic.ca>
Subject:        	Re: [Udpcast] Feature Requests: named sessions and no timeout messages
To:             	Don Bright <dbri.tcc at gmail.com>
Copies to:      	udpcast at udpcast.linux.lu

> 
> Actually the timeout messages are useful.  If you are
> imaging a bunch of machines at once, and one has
> a flaky ethernet device which is slowing down the
> process, the timeout provides info on which one is behind
> and might better be yanked from the process to allow the
> others to complete.
> 
> But as an option, it could be useful to some people.
> 
> --Donald Teed
> 
> 
> On Mon, 26 Jun 2006, Don Bright wrote:
> 
> > Dear UDP Casters,
> >
> > First let me say thank you for making this program. It has enabled me
> > to completely get rid of Symantec Ghost and it's damnable boot
> > floppies, as well as extremely hard to understand licensing
> > arrangement (I was never sure if I had a legal copy or not, someone
> > else at the workplace just gave me a copy of it, and I couldnt get any
> > information on the license for it)
> >
> > I have two feature requests.
> >
> > The first is to have an option, something like --name, which would
> > provide a 'name' for each 'session', so that if two people are using
> > udpcast on the same network, they wont conflict with each other. I
> > know they could just use different ports, but names seem easier than
> > ports (and certain ports might be blocked or conflict with other
> > programs)
> >
> > The second, is to have a command line option to stop the 'timeout'
> > messages on the sender. I'm sending 7 GB of data and getting 1%
> > timeout (maybe because im sending to some old machines) so you can
> > imagine the massive amounts of messages written to the console. I'd
> > like an option like --quiet or --hide-timeouts to stop this stuff.
> >
> > I might make a patch later on, but I thought I'd through this out
> > there in ccase someone has already done it or its being planned. Thank
> > you.
> > _______________________________________________
> > Udpcast mailing list
> > Udpcast at udpcast.linux.lu
> > https://lll.lgl.lu/mailman/listinfo/udpcast
> >
> _______________________________________________
> Udpcast mailing list
> Udpcast at udpcast.linux.lu
> https://lll.lgl.lu/mailman/listinfo/udpcast
> 


+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:mikes at kuentos.guam.net                            
  mailto:msetzerii at gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
+----------------------------------------------------------+

http://setiathome.berkeley.edu
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)


BOINC Seti at Home Total Credits 1378923.633697 


-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8 -- QDPGP 2.61c
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBRKBStSzGQcr/2AKZEQJTNQCdEUPg1RlICYz7GTs56IOqw9FUeIgAoJge
+LOUZXK5UFL7pdM045zUg2r0
=3/Zd
-----END PGP SIGNATURE-----