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 thing to do.  Here are two example scenarios 
under the current situation:

1 - when you're upgrading several servers, you get monitoring systems telling 
you that the process has stopped running… annoying
2 - when you upgrading in a FreeBSD jail *HOST*, the current approach will also 
stop the corresponding processes in any jails

#1 is annoying. 

#2 is downright unexpected.

I propose that we don't stop the processes at all.  Leave it up to the sysadmin 
to do the right thing.

They can decide to:

portupgrade
restart

or

stop
portupgrade
start

But this change gives them the choice.

Please discuss.

-- 
Dan Langille - http://langille.org


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users