Hi, Thanks for your report,
On Thu, Feb 26, 2015 at 04:43:50PM +0000, bertrand wrote: > Since /etc/dahdi/system.conf contains an error, dahdi_cfg will fail. > However, dahdi init script redirect dahdi_cfg stderr to /dev/null and > don't check dahdi_cfg exit code: > > if [ $system = debian ]; then > echo -n "Running dahdi_cfg: " > $DAHDI_CFG_CMD 2> /dev/null && echo -n "done" > echo "." > > Your only chance to notice something was wrong is the missing "done" > after "Running dahdi_cfg: ". > > Dahdi seems to start as expected, leaving your span as UNCONFIGURED, > which is quite misleading. I'll just note that in the Jessie version the preffered mode of operation would be not to use the init script at all and rely on running dahdi_cfg from a udev hook. In this case you'll have to find the error in the logs. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il | | a Mutt's tzaf...@cohens.org.il | | best tzaf...@debian.org | | friend -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
