Package: springgraph Version: 0.82-5 Severity: minor (Apologies if this bug report is a duplicate, my mta was borked) I recently completed a rather large springgraph picture ( 19518x18894 ) from a rather large .dot file, which took around 33 days to complete. Now, the picture turned out OK, thankfully, since I didn't run out ram, have the power cut out, have my operating system crash, and so on and so forth. In a perfect world, we'd all have an infinite amount of ram+swap, perfectly stable operating systems, userspaces, springgraph, and power companies, but since we don't live in such a world there's a significant chance that during a really long haul, springgraph for some reason be stopped, and all the work done towards making a picture (in my case, a month), would be lost. Would it be possible, even if as a commandline option, for there to be data saved in a temp file somewhere, every 500 "iterations" or so, so that in the case of a crash or something, that springgraph could reload said temp file, and continue with a rather large data set? Springgraph is an impressive tool, but such a feature might make it a little bit more robust and usable. Keep up the good work Jeffrey Cliff [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.livejournal.com/users/themusicgod1
-- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-386 Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) Versions of packages springgraph depends on: ii libgd-gd2-noxpm-perl 1:2.30-1 Perl module wrapper for libgd - gd ii perl 5.8.8-2 Larry Wall's Practical Extraction springgraph recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
