From owner-freebsd-questions@FreeBSD.ORG  Fri Sep 15 01:47:08 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CD9F116A403
	for <freebsd-questions@freebsd.org>;
	Fri, 15 Sep 2006 01:47:08 +0000 (UTC) (envelope-from on@cs.ait.ac.th)
Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 09BEC43D49
	for <freebsd-questions@freebsd.org>;
	Fri, 15 Sep 2006 01:47:07 +0000 (GMT) (envelope-from on@cs.ait.ac.th)
Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5])
	by mail.cs.ait.ac.th (8.13.1/8.12.11) with ESMTP id k8F1l7w5090944
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <freebsd-questions@freebsd.org>;
	Fri, 15 Sep 2006 08:47:07 +0700 (ICT)
Received: (from on@localhost)
	by banyan.cs.ait.ac.th (8.13.3/8.12.11) id k8F1l73F029577;
	Fri, 15 Sep 2006 08:47:07 +0700 (ICT)
Date: Fri, 15 Sep 2006 08:47:07 +0700 (ICT)
Message-Id: <200609150147.k8F1l73F029577@banyan.cs.ait.ac.th>
From: Olivier Nicole <on@cs.ait.ac.th>
To: freebsd-questions@freebsd.org
X-Virus-Scanned: on CSIM by amavisd-milter (http://www.amavis.org/)
Subject: Poutupgrade unsafe
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Sep 2006 01:47:08 -0000

Hi,

I know the mistake was on my side, I was not carefull enough when
using portupgrade on a production machine but...

Yesterday I froze our system for about one hour when I used
portupgrade to upgrade Samba. It was a very minor upgrade (from 3.0.10
to 3.0.23c,1 I think), but it happens that in between the 2 versions
the location of the password file for Samba has been changed.

I beleive that the port maintener has a very good reason why to change
this directory, but portupgrade would build and install the new Samba
silently (if the message at the begining of the makefile did ever
show, it was drawn into the flow of portupgrade messages) resulting
the new Samba did not accept any connection.

I think that such modification should be considered as critical and
portupgrade should stop and request acknowledgement before it keeps on
installing. I am not sure the mechanism exists in portupgrade, but I
see it as a very usefull enhancement.

Best regards,

Olivier