On 07/31/13 07:40, pietersnld wrote:
> Most of the ports on FreeBSD stop when you upgrade them.
No, they don't.
The vast majority leaves it to the admin to restart the processes.
Those who do stop, are somewhat expected to have a good reason to do so.
This isn't jusy my opinion, but the emerged
On Tuesday 30 July 2013 22:40:16 pietersnld wrote:
> Dan Langille wrote
> > This affects only FreeBSD users.
> >
> > At present, when upgrading sysutils/bacula-server or
> > sysutils/bacula-client, the port/package will stop bacula-dir & bacula-sd
> > (or bacula-fd respectively). This is done as
On Wed, Jul 31, 2013 at 3:35 PM, Martin Simmons wrote:
> > On Tue, 30 Jul 2013 14:06:21 -0400, Dan Langille said:
> >
> > This affects only FreeBSD users.
> >
> > At present, when upgrading sysutils/bacula-server or
> sysutils/bacula-client, the port/package will stop bacula-dir & bacula-sd
>
> On Tue, 30 Jul 2013 14:06:21 -0400, Dan Langille said:
>
> This affects only FreeBSD users.
>
> At present, when upgrading sysutils/bacula-server or sysutils/bacula-client,
> the port/package will stop bacula-dir & bacula-sd (or bacula-fd
> respectively). This is done as part of the unin
Dan Langille wrote
> This affects only FreeBSD users.
>
> At present, when upgrading sysutils/bacula-server or
> sysutils/bacula-client, the port/package will stop bacula-dir & bacula-sd
> (or bacula-fd respectively). This is done as part of the uninstall before
> doing the subsequent install.
>
This affects only FreeBSD users.
At present, when upgrading sysutils/bacula-server or sysutils/bacula-client,
the port/package will stop bacula-dir & bacula-sd (or bacula-fd respectively).
This is done as part of the uninstall before doing the subsequent install.
I think this is not the ideal
