Date: Mon, 10 Mar 2008 10:35:00 GMT From: Chris Calvey <chris@securityforensics.co.uk> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/121554: Portupgrade: suspend/resume support Message-ID: <200803101035.m2AAZ0Yf039619@www.freebsd.org> Resent-Message-ID: <200803101040.m2AAe5pg083904@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 121554 >Category: ports >Synopsis: Portupgrade: suspend/resume support >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Mar 10 10:40:05 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Chris Calvey >Release: 7.0-RELEASE >Organization: Digital Investigations >Environment: FreeBSD epsilon.localdomain 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Tue Mar 4 18:09:03 GMT 2008 root@epsilon.localdomain:/usr/obj/usr/src/sys/EPSILON i386 >Description: Would it be possible to implement some mechanism where portupgrade could be suspended and resumed at a later date? I am in the process of rebuilding all of my ports due to a recent upgrade to FreeBSD 7.0. The release announcement advised portupgrade -fa. With over 800 ports installed on this system such an operation would take a long time. I am not able to leave the system up continuous, and have had to try to break the portupgrade down into managable steps by upgrading selected ports. The whole process has been very messy indeed. I have two other machines to upgrade, and even if I generate a set of binary packages, the process will still take some time to complete. A suggestion might be that portupgrade could capture say the kill signal, write it's current upgrade tree to disk and exit. On restarting portupgrade it would re-load the saved tree and continue. >How-To-Repeat: portupgrade -fa >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803101035.m2AAZ0Yf039619>