Hi Scott,
Why the NTP would be fixed for America/New_York timezone?
[]'s
MM
On Mon, Oct 20, 2008 at 1:37 PM, Scott Lawrence
<[EMAIL PROTECTED]> wrote:
> I have just checked (r13757-13758) in changes that replace the
> sipx_reset_cd script with two new scripts (descriptions follow).
> Please read all of this, as there are things here that you need
> to know:
>
> sipx-setup
>
> Configures the sipXecs-specific settings needed to make the
> system managable with sipXconfig. This script is intended to
> be used on a system that already has all the normal
> configuration complete (hostname, dns, ntp, etc).
>
> Developer Note:
> This should be all you need to set up a system built from
> source, and does not require that it be run as root
> (running as the SIPXPBXUSER works).
>
> The script prompts the user to ask whether this system is the
> first sipXecs system or if this system is a new server being
> added to an existing cluster.
>
> First System:
>
> Prompts for the SIP Domain.
> Generates Certificates (CA & Host) using fixed
> organization name inputs & SIP Domain
> Generates a minimal domain-config file
> Enables sipXconfig so that sipXsupervisor will start it.
>
> Adding a server to an existing cluster:
>
> Prompts for:
> Master host name
> A setup password
> Fetches a setup tar file from master using basic auth w/
> https and untars it.
>
> NOTE:
> Fetching the setup file is not yet supported by
> sipXconfig (XCF-2615), so setting up a new distributed
> system will be a pain for a little while. I am checking
> this in anyway, because it will make testing the
> sipXconfig side easier.
>
> If you are running as root, it then configures sipXecs to be
> started by default and offers to start the services
> immediatly, otherwise it displays the command you should use
> to start sipXecs.
>
> sipx-setup-system
>
> This replaces sipx_reset_cd - it initializes the system
> services required by sipXecs, and then runs sipx-setup.
> This script must be run as root to actually do anything, since
> nearly everything it is supposed to do requires root
> privileges, but it can be run by anyone - run this way it
> doesn't actually do much except log what it would have done
> into its log file:
> .../var/log/sipxpbx/sipx-setup-system.log
>
> Prompts for and sets:
> Root password
> Hostname
> eth0 IP address/mask, gateway, dns servers
>
> Attempts to start the network.
>
> NOTE:
> The current version does _not_ configure and start a local
> DNS server. The plan is to add the capability to manage a
> local DNS server into sipXconfig, so this script just sets
> /etc/resolv.conf to the external servers. This may need to
> be revisited as we refine our ideas on managing DNS from
> sipXconfig (it's a bit of a chicken-and-egg problem).
>
> Set up NTP using fixed values:
> Timezone is set to Americas/New_York
> NTP servers are set to {0,1,2}.us.pool.ntp.org
> It then attempts to set the time using NTP; if that fails,
> the time is set to midnight January 1st 2008. Since
> sipXconfig now displays the time and provides ways for the
> administrator to change it, starting the clock in the past
> is ok.
>
>
>
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
>
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
