ports-mngmt/portmaster fetch process
jhell at DataIX.net
Sun Jan 10 03:17:27 UTC 2010
-----BEGIN PGP SIGNED MESSAGE-----
On Sat, 9 Jan 2010 22:07, jhell@ wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Curious if I can get your comments about a possible change in portmaster
> to change the behavior of its fetch method.
> While currently its fetch method is optimal for a environment that has a
> speedy ultra-fast connection, it runs havoc on a dial line "56k with
> speed-boost ;)"
> Would it be possible to: ?
> 1) Add a switch that changes its behavior to single fetches - or -
> 2) Change the default of multiple fetches to single.
> I opt for (2). as I really see no need have more then one fetch present at
> a time since it will wait for all others to finish anyway.
> The problem I am noticing is that fetches that are over the amount of
> three consecutive connections just revolve until others have finished
> causing DNS lookups on a line that is already at full speed and resulting
> in slower transactions of the first three connections.
> If there is something that I have looked over in the script then please
> excuse me but I have not noticed a predetermined way to change this as it
> stands right now.
> - --
> Sat Jan 9 21:47:25 2010
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (FreeBSD)
> -----END PGP SIGNATURE-----
I Killed the portmaster process with a ^C and the fetch process that were
initiated during run were left behind and not terminated after portmaster
has printed "Terminated" for the same amount of fetches that were left.
Though this does not bother me I thought I would give you a heads up on
Sat Jan 9 22:12:26 2010
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the freebsd-ports