summaryrefslogtreecommitdiff
path: root/xpp/xpp_sync
diff options
context:
space:
mode:
authorTzafrir Cohen <tzafrir.cohen@xorcom.com>2009-03-16 15:01:14 +0000
committerTzafrir Cohen <tzafrir.cohen@xorcom.com>2009-03-16 15:01:14 +0000
commit51c06791324573a771799dd3f39efa8fb72516d9 (patch)
treed25f7d25149efa501193e24d95e90718a77240b1 /xpp/xpp_sync
parent094878194250aa5f3a5f76447aa5a195c9f7a7dc (diff)
dahdi.init: call xpp_sync a bit later.
xpp_sync needs to only be called after dahdi_cfg was run, because the application of system.conf may change the priority of a PRI module span (If it is a sync provider, "NT", priority is lower). Also some documentation-only changes for xpp_sync. git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@6167 a0bf4364-ded3-4de4-8d8a-66a801d63aff
Diffstat (limited to 'xpp/xpp_sync')
-rwxr-xr-xxpp/xpp_sync13
1 files changed, 13 insertions, 0 deletions
diff --git a/xpp/xpp_sync b/xpp/xpp_sync
index 8d85739..e62169a 100755
--- a/xpp/xpp_sync
+++ b/xpp/xpp_sync
@@ -200,14 +200,27 @@ The parameter it is called with defaults to
I<auto>, but it is possible to override that parameter (e.g: set it to
I<dahdi>) through the value of XPP_SYNC in /etc/dahdi/init.conf .
+It should be run after dahdi_cfg as the configuration of a PRI module
+is set from it. It must be run after dahdi_registration as it only
+handles XPDs that are registered spans.
+
=head1 FILES
=over
+=item /sys/bus/astribanks/drivers/xppdrv/sync
+
+The low-level interface used by xpp_sync to set / read registration.
+
=item /proc/xpp/sync
+(Deprecated: no longer supported)
xpp_sync is essentially a nicer interface to /proc/xpp/sync . That file
shows the current xpp sync master (and in what format you need to write
to it to set the master).
+=head1 SEE ALSO
+
+dahdi_registration(1), dahdi_cfg(1), README.Astribank
+
=back