search for: 4173

...1/brick > ------------------------------------------------------- > Cumulative Stats: > Block Size: 4096b+ 8192b+ > 16384b+ > No. of Reads: 0 0 > 0 > No. of Writes: 1576 4173 > 19605 > Block Size: 32768b+ 65536b+ > 131072b+ > No. of Reads: 0 0 > 0 > No. of Writes: 7777 1847 > 657 > %-latency Avg-latency Min-Latency Max-Latency No...

...-------------------------------------------- >> Cumulative Stats: >> Block Size: 4096b+ 8192b+ >> 16384b+ >> No. of Reads: 0 0 >> 0 >> No. of Writes: 1576 4173 >> 19605 >> Block Size: 32768b+ 65536b+ >> 131072b+ >> No. of Reads: 0 0 >> 0 >> No. of Writes: 7777 1847 >> 657 >> %-latency Avg-latency...

...------------------ >>> Cumulative Stats: >>> Block Size: 4096b+ 8192b+ >>> 16384b+ >>> No. of Reads: 0 0 >>> 0 >>> No. of Writes: 1576 4173 >>> 19605 >>> Block Size: 32768b+ 65536b+ >>> 131072b+ >>> No. of Reads: 0 0 >>> 0 >>> No. of Writes: 7777 1847 >>> 657...

...es echocancelwhenbridged=yes rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1 immediate=no callerid="line1"< 238-20-31> channel => 1 callerid="line2"< 238-20-31> channel => 2 but Asterisk on startup reports that: WARNING[13326]: File chan_zap.c, Line 4173 (ss_thread): CallerID returned with rror on channel 'Zap/1-1' WARNING[14351]: File chan_zap.c, Line 4173 (ss_thread): CallerID returned with rror on channel 'Zap/2-1' and when I call the number that is supposed to terminate there I get busy signal. also in the zttool I see stran...

Asterisk 1.2.13 I am trying to figure out the best way for a night bell at work. Note: I have no spare buttons available on the phones. But I do have two lines and two park positions as buttons. Option 1 (easiest and the one I just implemented) When asterisk is in night mode, Connect to IVR, List all options and then if they dial 0 or timeout, ring every phone in the

...t root 4578 Dec 18 2020 upsd.conf.sample -rw-r----- 1 root root 2292 Dec 22 07:11 upsd.users -rw-r--r-- 1 root root 2131 Dec 18 2020 upsd.users.sample -rw-r--r-- 1 root root 15569 Jan 10 10:20 upsmon.conf -rw-r--r-- 1 root root 15313 Dec 18 2020 upsmon.conf.sample -rw-r--r-- 1 root root 4173 Jan 10 10:22 upssched.conf -rw-r--r-- 1 root root 3895 Dec 18 2020 upssched.conf.sample -rwxr-xr-x 1 root root 810 Jan 10 10:29 upssched-execscript.sh Do all that seem right to you? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debi...

Hello, Could save.image() be redesigned so that it promptly responds to Ctrl+C? It prevents the command line from being used for a number of hours if the contents of the workspace are large. -------------------------------------- Dario Strbenac University of Sydney Camperdown NSW 2050 Australia

Hi, I am trying to get a SIP extension's status without actually making a call. I am using sofia-sip's "options" example utility and the sip clients are SJphone softphones.

...u 1.0.11-2 (from Archlinux repository) Everything looks pretty unremarkable while using the computer normally running X which is very stable, can run for days. Also terminating the X server looks uneventful. *** *** Starting the second X-server hangs... *** [root at optiplex ~]# ps axf | grep X 4173 pts/1 D+ 0:00 | \_ /usr/bin/Xorg.wrap [root at optiplex ~]# cat /proc/4173/wchan rpm_resume [root at optiplex ~]# cat /proc/4173/syscall 2 0x7fffc7a788c0 0x2 0x7fffc7a788ce 0x690 0x7f0c3e0ed140 0x0 0x7fffc7a77fb0 0x7f0c3e06a330 [root at optiplex ~]# cat /proc/4173/sta...

...ze() and then exit. R also passes make check after the applied patch. Do these changes make sense, or am I overlooking some other problem? -- Best regards, Ivan -------------- next part -------------- A non-text attachment was scrubbed... Name: interrupt-serialize.patch Type: text/x-patch Size: 4173 bytes Desc: not available URL: <https://stat.ethz.ch/pipermail/r-devel/attachments/20230502/ab1d7f31/attachment.bin>

...chine as shown in the tables below. [Standalone/Embedded - same node] # of tasks Before patch After patch %Change ---------- ----------- ---------- ------- 3 2324/2321 2248/2265 -3%/-2% 4 2890/2896 2819/2831 -2%/-2% 5 3611/3595 3522/3512 -2%/-2% 6 4281/4276 4173/4160 -3%/-3% 7 5018/5001 4875/4861 -3%/-3% 8 5759/5750 5563/5568 -3%/-3% [Standalone/Embedded - different nodes] # of tasks Before patch After patch %Change ---------- ----------- ---------- ------- 3 12242/12237 12087/12093 -1%/-1% 4 10688/10696 10507/10521...

Sorry about that ./configure --with-included-popt But then 200+ plus lines of warnings :( I'll read some more -pete

...03 4162 4153 5977 2124 762 853 4153 8304 c: 4302 2157 4301 4289 6021 2072 806 879 4292 8584 ./imaptest list=0 dele=10 expu=10 seed=1 secs=60 msgs=100000 clients=10 Logi Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo u: 3211 1637 3206 3195 4639 1537 287 302 3202 6402 m: 2957 1508 2955 2944 4173 1440 279 306 2948 5894 c: 3933 1929 3933 3920 5604 2020 380 379 3923 7846 ------ ./imaptest list=0 dele=10 expu=10 seed=1 secs=60 msgs=100000 clients=1 Logi Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo u: 1529 745 1529 1528 2184 819 136 162 1528 3056 c: 1579 813 1579 1578 2257 811...

...chine as shown in the tables below. [Standalone/Embedded - same node] # of tasks Before patch After patch %Change ---------- ----------- ---------- ------- 3 2324/2321 2248/2265 -3%/-2% 4 2890/2896 2819/2831 -2%/-2% 5 3611/3595 3522/3512 -2%/-2% 6 4281/4276 4173/4160 -3%/-3% 7 5018/5001 4875/4861 -3%/-3% 8 5759/5750 5563/5568 -3%/-3% [Standalone/Embedded - different nodes] # of tasks Before patch After patch %Change ---------- ----------- ---------- ------- 3 12242/12237 12087/12093 -1%/-1% 4 10688/10696 10507/10521...

...chine as shown in the tables below. [Standalone/Embedded - same node] # of tasks Before patch After patch %Change ---------- ----------- ---------- ------- 3 2324/2321 2248/2265 -3%/-2% 4 2890/2896 2819/2831 -2%/-2% 5 3611/3595 3522/3512 -2%/-2% 6 4281/4276 4173/4160 -3%/-3% 7 5018/5001 4875/4861 -3%/-3% 8 5759/5750 5563/5568 -3%/-3% [Standalone/Embedded - different nodes] # of tasks Before patch After patch %Change ---------- ----------- ---------- ------- 3 12242/12237 12087/12093 -1%/-1% 4 10688/10696 10507/10521...

...> [Standalone/Embedded - same node] > # of tasks Before patch After patch %Change > ---------- ----------- ---------- ------- > 3 2324/2321 2248/2265 -3%/-2% > 4 2890/2896 2819/2831 -2%/-2% > 5 3611/3595 3522/3512 -2%/-2% > 6 4281/4276 4173/4160 -3%/-3% > 7 5018/5001 4875/4861 -3%/-3% > 8 5759/5750 5563/5568 -3%/-3% > > [Standalone/Embedded - different nodes] > # of tasks Before patch After patch %Change > ---------- ----------- ---------- ------- > 3 12242/12237 12087/12093 -1%/-...

...> [Standalone/Embedded - same node] > # of tasks Before patch After patch %Change > ---------- ----------- ---------- ------- > 3 2324/2321 2248/2265 -3%/-2% > 4 2890/2896 2819/2831 -2%/-2% > 5 3611/3595 3522/3512 -2%/-2% > 6 4281/4276 4173/4160 -3%/-3% > 7 5018/5001 4875/4861 -3%/-3% > 8 5759/5750 5563/5568 -3%/-3% > > [Standalone/Embedded - different nodes] > # of tasks Before patch After patch %Change > ---------- ----------- ---------- ------- > 3 12242/12237 12087/12093 -1%/-...

...ir tasks lock queue lock queue lock ------ ------- ---------- ---------- 1 135 135 137 2 890 1082 613 3 1932 2248 1211 4 2829 2819 1720 5 3834 3522 2461 6 4963 4173 3715 7 6299 4875 3749 8 7691 5563 4194 Executing one task per node, the performance data were: # of Ticket Fair Unfair nodes lock queue lock queue lock ------ ------- ---------- ---------- 1 135...

...1278 1280 1452 1482 1519 1520 1595 1626 1641 1656 1667 1688 1702 1703 1724 1758 2184 2187 2798 2883 2932 3034 3198 3202 3206 3230 3371 3432 3454 3457 3466 3467 3507 3519 3631 3637 3685 3702 3703 3716 3765 3798 3799 3803 3853 3854 3855 3857 3873 3885 3886 3962 3969 4024 4033 4050 4051 4058 4161 4166 4173 4176 4224 4273 4345 4400 4401 4436 4461 4490 4491 4498 4561 4595 4618 4651 4676 4711 4712 4713 4729 4731 4736 4737 4738 4739 4746 4786 4787 4788 4813 4816 4822 4847 4883 4885 4933 4941 4942 4957 4958 5029 5052 5097 5135 5136 5182 5217 5253 5271 5357 5543 5551 5565 5577 5589 5602 5612 5643 5692 5722...

Hi! Some systems I have take some time to shut down, so I would like them to shut down if the UPS have been on battery for 2 minutes. Internet has told me that SHUTDOWNCMD ?/sbin/shutdown -h +0? in /etc/nut/upsmon.conf will execute when the UPS is both OB (on battery) and LB (Low battery). Like in wiki.ipfire.org - Detailed NUT Configuration<https://wiki.ipfire.org/addons/nut/detailed>