Date: Tue, 23 Dec 2003 19:23:32 -0800 (PST) From: Jochen Gensch <incmc@gmx.de> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/60534: portupgrade not working if started by cron or if closing remote session after start Message-ID: <200312240323.hBO3NW7J033281@www.freebsd.org> Resent-Message-ID: <200312240330.hBO3UKiT034107@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 60534 >Category: ports >Synopsis: portupgrade not working if started by cron or if closing remote session after start >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 23 19:30:20 PST 2003 >Closed-Date: >Last-Modified: >Originator: Jochen Gensch >Release: 4.8 and 5.1 >Organization: >Environment: FreeBSD jesus 4.8-RELEASE-p13 FreeBSD 4.8-RELEASE-p13 #0: Sun Oct 5 17:19:27 CEST 2003 status@jesus:/mnt/daten/usr/obj/mnt/daten/usr/src/sys/ROUTINGKERNEL i386 >Description: If you start portupgrade by cron or if you start it remotely, then it will start properly but it always stops sometime and there is no useful log. It is even worse. Ports that should have been updated are deleted instead! The only way to do a proper portupgrade run is not closing the remote (ssh) session until it has finished or starting directly on the consle of that machine. That problems appeard on all my machine, 4.8 and 5.1. >How-To-Repeat: Just repeat the above procedures -> try running a portupgrade by cron or start a portupgrade through ssh an close ssh session after started. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312240323.hBO3NW7J033281>