From: Leo Famulari <leo@famulari.name>
To: Sergei Trofimovich <slyfox@inbox.ru>
Cc: 26811@debbugs.gnu.org
Subject: bug#26811: guix does not resume download on FTP timeouts
Date: Sun, 7 May 2017 14:58:17 -0400 [thread overview]
Message-ID: <20170507185817.GB27949@jasmine> (raw)
In-Reply-To: <20170507194932.213380f8@sf>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Sun, May 07, 2017 at 07:49:32PM +0100, Sergei Trofimovich wrote:
> On Sun, 7 May 2017 14:25:43 -0400
> Leo Famulari <leo@famulari.name> wrote:
>
> > On Sun, May 07, 2017 at 09:31:59AM +0100, Sergei Trofimovich wrote:
> > > I have slow internet :)
> > >
> > > It looks like ftp://tug.org has a FTP session timeout of 2 hours 11 minutes, or something like that.
> > > Over night I tried to build sbcl and failed. Note how download silently stopped at ~80% [1].
> > >
> > > Would be nice if guix had a mechanism to reconnect to FTP and continue download after timeout.
> >
> > In the meantime, you can download the files with a resumable tool like
> > wget, and then use `guix download file:///path/to/file` to work around
> > this missing feature. Note that both the client *and* the server must
> > support resuming downloads for this to work.
>
> The workaround worked.
>
> I've noticed it took guix-daemon 2GB of RAM to process this file locally.
> Does guix keep all the file in RAM until download finishes?
I haven't looked, but that's how I'd expect it be coded. The OS can
handle paging things in and out as needed, right?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-07 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 8:31 bug#26811: guix does not resume download on FTP timeouts Sergei Trofimovich
2017-05-07 18:25 ` Leo Famulari
2017-05-07 18:49 ` Sergei Trofimovich
2017-05-07 18:58 ` Leo Famulari [this message]
2017-05-08 14:27 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170507185817.GB27949@jasmine \
--to=leo@famulari.name \
--cc=26811@debbugs.gnu.org \
--cc=slyfox@inbox.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).