gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Cygwin tla binary snapshot for Windows


From: John Meinel
Subject: Re: [Gnu-arch-users] Cygwin tla binary snapshot for Windows
Date: Thu, 08 Jul 2004 02:59:27 -0500
User-agent: Mozilla Thunderbird 0.7 (Windows/20040616)

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


address@hidden wrote:
|>Why are we spawning a process for each patch get? Is it simply a tla
|>fork so that we can have asynchronous communication? Whatever happened
|>with the pipelining ideas? I believe it was implemented for sftp (which
|>I use), though it's not official.
|
|
| to use an external program (like tar, gz, patch etc.) you need
| to fork()/exec()... it's like that,
| if you do "cat file | gzip -d | tar xf -"
| your shell will go
|
|   if (fork()) { exec(tar xf-); }
|   else if (fork()) { exec(gzip -d); }
|   else { write(STDOUT, tar.gz-compressed-bytes); }
|
| That's the reason to use libtar, libz etc, so we can just call tar("zxf
| file")

Actually, I understand that part completely. What I didn't understand is
what process is being spawned specifically for "http get". I would have
thought that tla was connecting over the socket itself and negotiating
the conversation, not spawning a processes to do the download.

|
|
|>Well, strace on cygwin is a different beast than strace on linux. I'm
|>not sure why. It seems vastly more verbose.
|
|
| yes, that why I always use "grep" after it :-)
|
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA7P7fJdeBCYSNAAMRAkH6AKCYD8MVJRz8yrpIr0ELx/YVkXbK7wCfVZev
vBJC9Cw1qCbsjhXNCspXVTU=
=36To
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]