[ale] ALE puzzler (or, BusyBox rocks)

[JK]

Ah, OK, hmm.  Reading the nc manpage, it says it stays open until
the *network* side gets shut down. In light of that, the behavior
I saw (nc exiting as soon as it was done reading from tar,
apparently) confuses me. I had nc running on both sides of the
connection, so it's not clear what would make either of them
decide to quit.


James Sumners wrote:
> Hmmm. Typically when I do that netcat keeps running, waiting for more
> input. I haven't done it in a long time, though.
> 
> Oh! I just remembered. I usually do `tar cvf - . | bzip2 -9 - | nc
> host port`. So bzip2 is probably causing the hangup.
> 
> On Thu, Feb 26, 2009 at 3:54 PM, JK <jknapka at kneuro.net> wrote:
>> James Sumners wrote:
>>> Uh, yeah. That's how I typically backup my Linux machines before
>>> reloading them (new distro or whatnot). One helpful thing to do is
>>> have tar print what file it is working on. That way you know when it
>>> has stopped working so you can hit ctrl+\.
>>
>> In this case both tar and nc exited when they were done.
>> Under what circumstance would that not be the case?
>>
>> -- JK
> 
> 
> 


-- 
I do not particularly want to go where the money is -
  it usually does not smell nice there. -- A. Stepanov