For minimum downtime just leave FS running, go to where you have the FS source and do: git pull make /etc/init.d/freeswitch stop make install /etc/init.d/freeswitch start That's assuming you have a freeswitch init script. That'll leave you with only the downtime that it takes to restart FS, and the length of the make install(usually very short). William King Senior Engineer Quentus Technologies, INC 1037 NE 65th St Suite 273 Seattle, WA 98115 Main: (877) 211-9337 Office: (206) 388-4772 Cell: (253) 686-5518 william.king@quentustech.com On 04/30/2012 11:52 AM, Kerem Erciyes wrote:
Or you could always build a debian-live image that includes freeswitch-current and all the wanpipe driver etc, and swap them out at will at 5 mins downtime maximum, store all you data on HDD of /etc and /freeswitch/conf and you are good to go....
On Tue, Apr 17, 2012 at 12:02 AM, Michael Collins <msc@freeswitch.org <mailto:msc@freeswitch.org>> wrote:
On Mon, Apr 16, 2012 at 12:01 PM, Jason Moran <jmoran@secureachsystems.com <mailto:jmoran@secureachsystems.com>> wrote:
Sorry for such a basic question:
1. If I do a 'make current' while a system is running it will not have any effect until I restart FS, correct?
2. What if 'make current' fails? What if it fails and the server gets restarted, will FS work?
3. Is it more advisable to stop FS, do the 'make current', then start FS even though it will have a longer down time?
I know it's best to keep FS up-to-date -- but it is difficult when you only have 1 system available and it is expected to have 100% uptime..
Thanks, Jason
Since you don't have a spare system (which is totally naughty, btw, especially if your corporate overlords expect 100% uptime) then my next question would be this: how are you set on CPU power, RAM, and disk space? The reason I ask is that it is entirely possible to create a secondary git clone of the FS repo and use a completely different install path when running the configure script. You could "make current" in that secondary repo and get a sort of preview of what would happen w/o touching your production build env or install dirs. If the update goes well in your test scenario then you could do the update in your production environment.
It's kinda hackish but if you have spare disk space then it's a really cheap option. It isn't perfect, but it does give you at least some semblance of "try before you buy."
-MC
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Kerem Erciyes - Sistem Danismani http://keremerciyes.com
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org