Re: [Bacula-users] HEADS UP: change to FreeBSD port coming
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 consensus from a general discussion on freebsd-questions (IIRC). bye -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] HEADS UP: change to FreeBSD port coming
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 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 > > Hello, > > Most of the ports on FreeBSD stop when you upgrade them. When I upgrade > bacula I always restart fd, dir and sd after upgrading otherwise the new > program is not loaded and the old version is still used. If that's the > behavior you want why upgrade in the first place. > In my opinion its the right thing to do when uninstalling a port otherwise > the program is still running even if its removed! Did a rm -rf once on the > wrong directory and all programs kept running. Had to reinstall them all > because after a reboot they would not start again because the executables > were missing. > I think sysadmins will know what to do when upgrading. > > Greetings, > Pieter To my mind it's not a problem at all when programs keep running after upgrade. Sometimes it's even good, because whatever these program do while upgrading, they can peacefully finish doing it (eg. SD accepting a backup). If I want to make sure that the program isn't running while upgrading, I just stop it before upgrading. -- Silver -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] HEADS UP: change to FreeBSD port coming
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
> (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.
>
> It may not be ideal for upgrading, but it also applies to fully
> uninstalling.
> I don't know what the FreeBSD convention is for daemons in general but
> there
> are quite a few in /usr/ports/net that stop themselves on uninstall.
>
>
> > 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 think the use of killall is the problem in #2. It would be better to
> stop
> the daemons with the bacula-ctl-* tools (or rc.d entries) so it will only
> kill
> the correct ones.
>
>
> > 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
>
> I've never liked that order because it assumes that the new version's stop
> script will work with the old version's running program.
>
> __Martin
>
>
> --
> 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@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
Hello,
In our servers we have within /usr/local/etc/pkgtools.conf something like:
AFTERINSTALL = {
'sysutils/bacula-client' => proc { |origin| cmd_restart_rc(origin) },
# followed by similar entries for mysql55-server, apache22, net-snmp,
openldap24-server etc..
}
Regards,
Panagiotis
--
Panagiotis Christias
christ...@gmail.com
--
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] HEADS UP: change to FreeBSD port coming
> 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 uninstall before doing the > subsequent install. > > I think this is not the ideal thing to do. It may not be ideal for upgrading, but it also applies to fully uninstalling. I don't know what the FreeBSD convention is for daemons in general but there are quite a few in /usr/ports/net that stop themselves on uninstall. > 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 think the use of killall is the problem in #2. It would be better to stop the daemons with the bacula-ctl-* tools (or rc.d entries) so it will only kill the correct ones. > 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 I've never liked that order because it assumes that the new version's stop script will work with the old version's running program. __Martin -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] HEADS UP: change to FreeBSD port coming
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. > > 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@.sourceforge > https://lists.sourceforge.net/lists/listinfo/bacula-users Hello, Most of the ports on FreeBSD stop when you upgrade them. When I upgrade bacula I always restart fd, dir and sd after upgrading otherwise the new program is not loaded and the old version is still used. If that's the behavior you want why upgrade in the first place. In my opinion its the right thing to do when uninstalling a port otherwise the program is still running even if its removed! Did a rm -rf once on the wrong directory and all programs kept running. Had to reinstall them all because after a reboot they would not start again because the executables were missing. I think sysadmins will know what to do when upgrading. Greetings, Pieter -- View this message in context: http://bacula.10910.n7.nabble.com/HEADS-UP-change-to-FreeBSD-port-coming-tp76024p76029.html Sent from the Bacula - Users mailing list archive at Nabble.com. -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] HEADS UP: change to FreeBSD port coming
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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
