Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Sep 2006 09:50:20 +0200
From:      "Hans F. Nordhaug" <Hans.F.Nordhaug@hiMolde.no>
To:        freebsd-ports@freebsd.org
Subject:   Re: portupgrade and starting servers after upgrade.
Message-ID:  <20060919075020.GA27670@hiMolde.no>
In-Reply-To: <20060919074600.GA720@turion.vk2pj.dyndns.org>
References:  <450F7A78.5020007@gneto.com>  <20060919074600.GA720@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
* Peter Jeremy <peterjeremy@optushome.com.au> [2006-09-19]:
> On Tue, 2006-Sep-19 07:04:56 +0200, Martin Nilsson wrote:
> >For instance every time I portupgrade dhcpd I have to remember to start 
> >it manually after the upgrade. As portupgrade knows how to stop the 
> >daemon before the upgrade it should also know how to start it afterwards.
> 
> Stopping the daemon is easy: "/usr/local/etc/rc.d/.... stop".
> Starting it afterwards is not quite as easy because, portupgrade
> should restore the state of the daemon to the state prior to it
> starting, not just start it automatically.  (The administrator
> may have manually stopped the daemon).

Good point, but isn't it as easy to check the status before stopping
it: "/usr/local/etc/rc.d/.... status"? You could even check the
reported pid. If the status is in some way unclear to portupgrade,
portupgrade could warn the user - "Service X not started again -
unknown status". Or am I doing it too easy?

Hans



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060919075020.GA27670>