> Is there a policy about how to deal with running daemons and portupgrade?
>
> 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.
>
On 9/19/06, Hans F. Nordhaug <[EMAIL PROTECTED]> wrote:
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 - "Servic
On Tue, Sep 19, 2006 at 05:46:00PM +1000 I heard the voice of
Peter Jeremy, and lo! it spake thus:
>
> Stopping the daemon is easy: "/usr/local/etc/rc.d/ stop".
More to the point, portupgrade doesn't stop it. pkg_delete does,
because stopping it is in the plist. e.g., for spamassassin:
% g
* Peter Jeremy <[EMAIL PROTECTED]> [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 als
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 i
Is there a policy about how to deal with running daemons and portupgrade?
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.
/Mart
