xpp_sync(8) [debian man page]

XPP_SYNC(8)						User Contributed Perl Documentation					       XPP_SYNC(8)

NAME

       xpp_sync - Handle sync selection of Xorcom Astribanks.

SYNOPSIS

       xpp_sync <auto|dahdi|nn>

       xpp_sync [-v]

DESCRIPTION

       On a normal operation one Astribank device provides timing for all the other Astribank devices.

       When run without parameters, xpp_sync will display a list of Astribanks (xbuses) that are connected and registered as Dahdi spans. The
       current xpp sync master will be marked.

       If you this an Astribank is connected and yet it does not appear on the output of xpp_sync, it may be unregistered. Try running
       dahdi_registration .

   Parameters
       auto
	   Automatically selects the best Astribank for syncing.

       dahdi
	   Gets synchronization from the Dahdi sync master.

       nn  Sets XBUS-nn as sync source.

       -v  Also print the numeric xpp sync rank.

       (Parameter name is case-insensitive)

   Example output:
	       Setting SYNC
	       Current sync: 01
	       Best Available Syncers:
		+ XBUS-01 (usb-0000:00:10.4-3) [usb:12345678]	    [ PRI_TE PRI_NT PRI_TE PRI_NT ]
		  XBUS-00 (usb-0000:00:10.4-2) [usb:QA-01]	    [ FXS FXO ]
	       ==================================================
	       WARNING: FXO which is not the syncer cause bad PCM
			Affected Astribanks are:
	       --------------------------------------------------
		       XBUS-00
	       ==================================================

       In this example we see that the recommended xpp sync master is XBUS-02 - it is the first on the list. It is also the actual syncer, as we
       can see from the '+' beside it.

       xpp_sync is normally called from the dahdi init.d script.  The parameter it is called with defaults to auto, but it is possible to override
       that parameter (e.g: set it to dahdi) through the value of XPP_SYNC in /etc/dahdi/init.conf .

FILES

       /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).

SEE ALSO

       dahdi_registration(1), dahdi_cfg(1), README.Astribank

perl v5.14.2							    2009-09-30							       XPP_SYNC(8)

ASTRIBANK_IS_STARTING(8)												  ASTRIBANK_IS_STARTING(8)

NAME

       astribank_is_starting - Mark / check is a Xorcom Astribank (xpp) is starting

SYNOPSIS

       astribank_is_starting [-d] [-v] [-t timeout] <-a|-r|-w>

       astribank_is_starting [-d] [-v]

       astribank_is_starting -h

DESCRIPTION

       astribank_is_starting is an internal tool used by various xpp scripts to mark that there may be an Astribank device currently initializing,
       and to check for that mark.

       Technically the mark is a SysV semaphore.

OPTIONS

       -a
	      Add.  Set the mark. Should return 0 unless there's an error.

       -r
	      Remove.  Reset the mark. Should return 0 unless there's an error.

       -ttimeout
	      Timeout.	Set the timeout value for the -w option. Default is 60 seconds.

       -w
	      Wait.  Wait for mark to be reset. Should return 0 unless there's an error.

       Without -a or -r: return 0 if the mark has been set, or a non-zero value otherwise.

       -d
	      Print debug information to stderr.

       -v
	      Verbose execution.

       -h
	      Displays usage message.

FILES

       /proc/sysvipc/sem
	      If set, the astribank should appear there with the ID 11211168 (0xAB11A0).  Naturally the ID (or rather, the usage of a semaphore in
	      the first place) is an implementation detail that may change.

NOTES

       astribank_is_starting  is used to mark the fact that an Astribank may be currently reenumerating (technically: distonnecting and connecting
       as a new USB device) after loading the firmware. Thus the script that loads the firmware (/usr/share/dahdi/xpp_fxloader) uses this  utility
       to set the mark.

       The mark is reset by /usr/share/dahdi/waitfor_xpds , which is typically run by the DAHDI init script and waits for all Astribanks to finish
       loading.

       Q: Why do you use a semaphore?

       A: because, unlike the filesystem, it is writable at any given time.

BUGS

       Option ordering matter. The -v and -d options should preceed the actions (-a, -r and -w).  The  -ttimeout  option  should  preceed  the	-w
       option.

SEE ALSO

       semctl(3)

AUTHOR

       This  manual  page  was written by Tzafrir Cohen <tzafrir.cohen@xorcom.com> .  Permission is granted to copy, distribute and/or modify this
       document under the terms of the GNU General Public License, Version 2 any later version published by the Free Software Foundation.

       On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.

								  16 August 2009					  ASTRIBANK_IS_STARTING(8)