search for: 14a4

Hi, We are testing Asterisk (1.2.5, configured for an IP PBX) for the number of simultaneous multiple VoIP calls supported. Whenever we increase the number of SIP end points over 250, or the equivalent of 125 caller-callee pairs, our testing fails. In fact, adding even one additional pair of end points over the 250 makes all end points fail. I have pasted the console diagnostics posted by

...6 06bd 05c6 07b6 0583 02906a0 0883 0528 097d 0505 0a71 04f9 0b23 04dc 02906b0 0beb 0502 0cc6 0564 0d6b 05aa 0df6 05eb 02906c0 0eb4 067a 0fad 0754 1072 07f8 10da 0846 02906d0 114e 08b1 11c8 093f 121c 09b8 128d 0a3d 02906e0 1318 0ac0 1396 0b20 141d 0b5e 1477 0b3c 02906f0 14a0 0aaf 14d1 09f1 14cb 08ed 14a4 07dd 0290700 In theory, must they deliver exactly the same audio output or some errors are tolerable. Thank you very much, Pattara -- Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html ----------------------------------------------...

Any progress here? Does anyone know if this will be fixed in 7.1 latest, or should we start looking for different backup solution (in this case I would suggest to remove dump from the source tree - having a backup tool that doesn't work is worse than having none). After upgrading we basically cannot backup our servers. Shouldn't this issue be on

While trying to speed up nanobsd builds, I mounted /usr/obj on a ramdisk and found my box crashing. Thinking it might be hardware, I tried a separate machine, but with the same results. I have 4G of ram (i386). Am I just running out of some kernel memory ? If so, is there anything I can adjust to prevent this, yet still use mfs in this way ? mdconfig -a -t malloc -s 1800M newfs /dev/md0

Hi If I have the wrong list please feel free to redirect me. I'm running 7.0-RELEASE-p4 and trying to backup to an external USB drive. I'm using the following command dump -a0Lf /backup/diskimages/root /dev/mfid0s1a Where df: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/mfid0s1a 507630 208436 258584 45% / /dev/da1s1d 709513458

Hi, after some time without FreeBSD I installed 7.1 on an IBM Thinkpad T30 (with ZFS root on encrypted geli, works great). Config is: FreeBSD hasking.alashan.nongo 7.1-STABLE FreeBSD 7.1-STABLE #3: Thu Feb 5 21:10:45 CET 2009 root@hasking.alashan.nongo:/usr/obj/usr/src/sys/HASKING i386 I tried using my ath based D-Link DWL G650, which still seems to have some issues in regard to interrupt

Hello, I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: cd /usr/src make buildworld make buildkernel KERNCONF=BLACK make installkernel KERNCONF=BLACK At this point I can reboot and all is good. After boot I install the new world: cd /usr/src mergemaster -p reboot into single user mode cd /usr/src make

...host.backup_rrds D:9aadf1370a68|audit] ('trackid=8cc9995210d2f92f33e12da4776cefb9' 'LOCAL_SUPERUSER' 'OpaqueRef:5005b228-e50d-0d6b-e4f9-8d85794ba15c' 'ALLOWED' 'OK' 'API' 'host.backup_rrds' (('host' 'lab-xh3' 'f0de05b1-f9fc-14a4-c98a-c88f8bc441ab' 'OpaqueRef:5005b228-e50d-0d6b-e4f9-8d85794ba15c'))) xenstore content: root at lab-xh3:~# xenstore-ls tool = "" xenstored = "" local = "" domain = "" 0 = "" name = "Domain-0" memory = "&quot...

I hope this isn't an invalid topic for this list. I'm on so many lists and I hate to join another one just to get help on one thing. Apologies if it's not. I am able to use ssh-keygen to generate keys so that I can ssh from my Mac to any of my SuSE systems or ssh from my Mac to any of my FreeBSD systems, without having to enter my password. When I try the same thing from a SuSE system

Hello! A machine I manage remotely for a friend comes under a distributed ssh break-in attack every once in a while. Annoyed (and alarmed) by the messages like: Aug 12 10:21:17 symbion sshd[4333]: Invalid user mythtv from 85.234.158.180 Aug 12 10:21:18 symbion sshd[4335]: Invalid user mythtv from 85.234.158.180 Aug 12 10:21:20 symbion sshd[4337]: Invalid user mythtv from 85.234.158.180 Aug 12

Hello! A machine I manage remotely for a friend comes under a distributed ssh break-in attack every once in a while. Annoyed (and alarmed) by the messages like: Aug 12 10:21:17 symbion sshd[4333]: Invalid user mythtv from 85.234.158.180 Aug 12 10:21:18 symbion sshd[4335]: Invalid user mythtv from 85.234.158.180 Aug 12 10:21:20 symbion sshd[4337]: Invalid user mythtv from 85.234.158.180 Aug 12

In http://www.freebsd.org/releases/7.0R/announce.html says Updating Existing Systems > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes > a major version upgrade, so no matter which method you use to update > an older system you should reinstall any ports you have installed on > the machine. This will avoid binaries becoming linked to inconsistent > sets

Can''t seem to fully boot a domU on either EM64T or Opteron with x86_64 xen-unstable. Both systems'' report this from xen: (XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR(00000000c0000100. (XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR(00000000c0000102. (XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR(00000000c0000080. They boot

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of