So I wanted to tie this up.
I stripped out all extra code I'd been messing with - waiting for STMh, using select, setting nonblocking, all the many things I tried - and moved my server to my linux laptop. Everything works fine. The buffer fullness climbs straight to 0.99 and hovers there; songs play through without a hitch. A blocking socket, writing 65536 bytes at a time, works perfectly well, exactly as I'd expect. Now what I have to do is figure out why a wired connection from a raspberry pi worked fine, and a wired connection from a laptop running Linux 4.15.0-55-generic, Mint, works fine, but an otherwise idle NUC running Linux 4.15.0-64-generic, Mint, with a wired connection to the same switch, stalls horribly (but somehow can manage other network traffic, like running a mumble server on occasion, without an issue.) I would not have believed it, and I will be playing with cables, switches and, probably, learning more about configuring TCP on linux than I ever wanted to. Or, I'll buy a $35 dollar pi to stream my music again. This is, frankly, creepy. I would never have considered Linux capable of stalling a socket so badly, especially when it has nothing else to do. I hope to mercy it's not some problem with the NUC hardware itself. Anyway, thanks for the support. ------------------------------------------------------------------------ ScottAM's Profile: http://forums.slimdevices.com/member.php?userid=69412 View this thread: http://forums.slimdevices.com/showthread.php?t=110986 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
