-begin-
write(1, "\nUse STOP NOW to shutdown Asteri"..., 35) = -1 EIO (Input/output erro r) write(1, "*CLI> ", 6) = -1 EIO (Input/output error) read(0, "", 1) = 0 ioctl(0, SNDCTL_TMR_STOP, {B38400 opost isig icanon echo ...}) = -1 EIO (Input/o utput error)
-end-
Mark kindly responded to me:
-begin-
In the mean time try running asterisk with no console. This is bug #864. Preliminary analysis shows that after a "restart now", one of the ioctl()'s performed by editline fails with "-1". Ignoring the ioctl made the CLI non-functional. Happy to get any help I can in this regard.
-end-
Hope this helps.
Cheers
Martin Pycko wrote:
try to do ps -auxm to list all the threads of the asterisk. Then connect with gdb to the thread that takes 99% of CPU and find out what it's doing.
Martin
On Mon, 22 Mar 2004, Bill Hamlin wrote:
Nope same problem. I just started it and did a couple of ps aux's and got this output:
[EMAIL PROTECTED] root]# ps aux|grep ast
root 20140 91.6 1.3 115880 6676 ? R 15:43 1:10
asterisk -vvvvvgcd
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
