On Wed, Jan 15, 2014 at 04:00:19AM +0000, Rodrigo Borges Pereira wrote: > Ok, I'm a believer now: > > > shell> chrt -f 99 patlooptest /dev/dahdi/1 -t 300 -vvvvv > Using Timeout of 300 Seconds > Going for it... > Timeout achieved Ending Program > Test ran 28295 loops of 2039 bytes/loop with 0 errors > > > Still, any hint about this? > > shell> lsof /dev/dahdi/2 > shell> > shell> chrt -f 99 patlooptest /dev/dahdi/2 -t 300 -vvvvv > /dev/dahdi/2: Device or resource busy > > Thanks.
Asterisk doesn't necessarily have to open channels via /dev/dahdi/<channel number>. In fact, they generally open /dev/dahdi/channel and then use the SPECIFY ioctl to bind that particular file descriptor to a specific dahdi channel. So try 'lsof /dev/dahdi/channel' and see what you see. Cheers, Shaun -- Shaun Ruffell Digium, Inc. | Linux Kernel Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
