Date: Thu, 14 Sep 2006 19:22:55 -0700 From: Pete Slagle <freebsd-questions@voidcaptain.com> To: Olivier Nicole <on@cs.ait.ac.th> Cc: freebsd-questions@freebsd.org Subject: Re: Poutupgrade unsafe Message-ID: <450A0E7F.5090400@voidcaptain.com> In-Reply-To: <200609150147.k8F1l73F029577@banyan.cs.ait.ac.th> References: <200609150147.k8F1l73F029577@banyan.cs.ait.ac.th>
next in thread | previous in thread | raw e-mail | index | archive | help
Olivier Nicole wrote: > 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. This one bit me too, but we have only ourselves to blame; there was a clear (well, pretty clear) warning of the change in /usr/ports/UPDATING. You would never forget to check UPDATING before running portupgrade would you? :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?450A0E7F.5090400>