search for: 7660

...d be) The spec doc says... " A two-byte, big-endian binary number signifying the number of header (non-audio) packets, including this one. " Here's a partial dump from a file created by flac.exe Page Location : 0 to 79 Ver No : 0 Head Flags : 2 Granule Pos : 0 Serial No : 7660 Seq No : 0 Checksum : 1670249472 Num Segs : 1 ------------------------ Head Size : 28 Data Size : 51 Page Size : 79 Num Packets : 1 ------ Packet 0 (51 bytes) ------- 00000000: 7F 46 4C 41 43 01 00 00 03 66 4C 61 43 00 00 00 ........ The 9th byte in says there are 3 headers (incl...

...e following data, which represent a monthly consumption of juices: >x<-scan() 1: 2859 3613 3930 5193 4523 3226 4280 3436 3235 3379 3517 6022 13: 4465 4604 5441 6575 6092 6607 6390 6150 6488 5912 6228 10196 25: 7612 7270 8617 9535 8449 8520 9148 8077 7824 7991 7660 12130 37: 9135 9512 9631 12642 11369 12140 13953 12421 11081 46: Read 45 items > arima(x,order=c(2,1,2), seasonal=list(order=c(0,1,0), period=12))->l > acf(l$resid) > sd(l$resid) > Box.test(l$resid) Now, my problem: 1. All the analysis that i have seen regarding ARIMA modeling,...

...car in an insurance category age is the age of policy holder dist is the district where the policy holder lived (1 for London and other major cities, and 0 otherwise) Data: car age dist y n 1 1 0 65 317 1 2 0 65 476 1 3 0 52 486 1 4 0 310 3259 2 1 0 98 486 2 2 0 159 1004 2 3 0 175 1355 2 4 0 877 7660 3 1 0 41 223 3 2 0 117 539 3 3 0 137 697 3 4 0 477 3442 4 1 0 11 40 4 2 0 35 148 4 3 0 39 214 4 4 0 167 1019 1 1 1 2 20 1 2 1 5 33 1 3 1 4 40 1 4 1 36 316 2 1 1 7 31 2 2 1 10 81 2 3 1 22 122 2 4 1 102 724 3 1 1 5 18 3 2 1 7 39 3 3 1 16 68 3 4 1 63 344 4 1 1 0 3 4 2 1 6 16 4 3 1 8 25 4 4 1 33 114...

...-6539 > -2.22% > Fast > 312787 > 294471 > 18316 > 6.22% > source + MI > 294979 > 294471 > 508 > 0.17% > ILP + MI > 296681 > 294471 > 2210 > 0.75% > BURR + MI > 289328 > 294471 > -5143 > -1.75% > Fast + MI > 302131 > 294471 > 7660 > 2.60% > > So, the best register pressure reduction scheduler is BURR. Note that enabling the MI scheduler makes things better when the SD scheduler is relatively weak at reducing register pressure (fast or ILP), while it makes things worse when the SD scheduler is relatively good at red...

Forgive my ignorance on this topic - I would like to build an LDAP server at our shop. We a native 2k3 domain and would like this Cent LDAP server to pull in all the info from AD. Then periodically, have the Cent server sync with new addition/subtractions of AD. Is there a How-To out there somewhere that someone can point me to? I don't want to recreate the wheel by hand-inputing information

...nd description format telephone-event Capabilities: us - 0xe (gsm|ulaw|alaw), peer - audio=0x104 (ulaw|g729)/video=0x0 (nothing), combined - 0x4 (ulaw) Non-codec capabilities: us - 0x1 (g723), peer - 0x1 (g723), combined - 0x1 (g723) Found user '2004' Aug 17 22:19:30 NOTICE[456]: chan_sip.c:7660 handle_request: Failed to authenticate user "2004" <sip:2004@192.168.1.30>;tag=53ED9FBF-D06765E2 Reliably Transmitting (no NAT): SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 192.168.1.37:5060;branch=z9hG4bK893143acACFB06A9 From: "2004" <sip:2004@192.168.1.30>;tag=53ED9FBF-...

...5551 5564 5567 5595 5598 5642 5794 5841 5896 5933 5960 5961 5994 6001 6005 6016 6017 6051 6075 6125 6152 6163 6215 6238 6239 6240 6241 6287 6311 6342 6350 6353 6357 6369 6431 6472 6689 6928 6945 6951 7026 7030 7045 7046 7115 7210 7212 7214 7230 7256 7295 7298 7340 7489 7490 7492 7654 7655 7658 7660 7676 7767 7768 7800 7801 7913 7937 7956 8075 8085 8102 8111 8144 8266 8329 8333 8394 8395 8431 30 OK Search completed (36.029 secs). 40 SEARCH text "coucou" * SEARCH 40 OK Search completed (0.002 secs). 50 SEARCH text "blabla" * SEARCH 50 OK Search completed (0.002 secs). 60 LO...

...ado. Promover Ajude-nos espalhar a palavra sobre CentOS e Enterprise Linux. Doa??o Fa?a uma doa??o para o projeto CentOS para operar este porjeto de software livre. Sobre Saiba mais sobre o projeto CentOS. -- att. _ ?v? Thiago Avelino /(_)\ Programador | SysAdmin ^ ^ Celular: (11) 7660-2933 www.avelino.us | www.centos-br.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20090203/ee122a48/attachment-0002.html>

...ows: ========================== [>>] Reading from client A00015 SELECT INBOX [<<] Reading from server * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 7668 EXISTS * 0 RECENT * OK [UNSEEN 7660] First unseen. * OK [UIDVALIDITY 1101063317] UIDs valid * OK [UIDNEXT 334080] Predicted next UID A00015 OK [READ-WRITE] Select completed. [>>] Reading from client A00016 UID FETCH 1:* (FLAGS RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS.NOT (RECEIVED)]) [<<] Reading from ser...

We use some Samba servers running SuSE 7.1 and samba 2.2.1a. These servers are sometimes very slow while delivering data over the network. It is like a short sleep-mode followed by a wake up. We use Win 95, 98 and 98SE Clients. Any ideas? Thanks from germany, Andre Klocke -------------- next part -------------- HTML attachment scrubbed and removed

hi list, I am happy being able to report, that I got winxp finally to run on my system. I have an ASUS T5600 Core 2 Duo with 1 Gig memory and SATA. Until the todays "apt-get dist-upgrade" I was''t able to get any graphical output out of the SDL-Window, but now it is thete and simply works, wonderful ! I attached my system info. Big thank to the xen-team and the debian people !

...-6539 > -2.22% > Fast > 312787 > 294471 > 18316 > 6.22% > source + MI > 294979 > 294471 > 508 > 0.17% > ILP + MI > 296681 > 294471 > 2210 > 0.75% > BURR + MI > 289328 > 294471 > -5143 > -1.75% > Fast + MI > 302131 > 294471 > 7660 > 2.60% > > So, the best register pressure reduction scheduler is BURR. Note that enabling the MI scheduler makes things better when the SD scheduler is relatively weak at reducing register pressure (fast or ILP), while it makes things worse when the SD scheduler is relatively good at red...

Hi all, I've set SELinux to disabled using the security and firewall widget but I'm still getting a lot of messages in Logwatch.... NULL security context for user, but SELinux in permissive mode, continuing () So it looks like SELinux is still operating. Can anyone tell me how to turn it off completely? It's my development server under my desk so I reallly don't care

It seems we are hitting a boundary with zfs send/receive over a network link (10Gb/s). We can see peak values of up to 150MB/s, but on average about 40-50MB/s are replicated. This is far away from the bandwidth that a 10Gb link can offer. Is it possible, that ZFS is giving replication a too low priority/throttling it too much?

...at64(3, {st_mode=S_IFREG|0755, st_size=88272, ...}) = 0 old_mmap(NULL, 65004, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40168000 madvise(0x40168000, 65004, MADV_SEQUENTIAL|0x1) = 0 old_mmap(0x40175000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xd000) = 0x40175000 old_mmap(0x40176000, 7660, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40176000 close(3) = 0 open("/lib/libattr.so.1", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 \r\0\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0...

...lls Spill Difference % Spill Difference Source 294471 294471 0 0.00% ILP 298222 294471 3751 1.27% BURR 287932 294471 -6539 -2.22% Fast 312787 294471 18316 6.22% source + MI 294979 294471 508 0.17% ILP + MI 296681 294471 2210 0.75% BURR + MI 289328 294471 -5143 -1.75% Fast + MI 302131 294471 7660 2.60% So, the best register pressure reduction scheduler is BURR. Note that enabling the MI scheduler makes things better when the SD scheduler is relatively weak at reducing register pressure (fast or ILP), while it makes things worse when the SD scheduler is relatively good at reducing register...

On Jul 2, 2013, at 2:35 PM, Ghassan Shobaki <ghassan_shobaki at yahoo.com> wrote: > Thank you for the answers! We are currently trying to test the MI scheduler. We are using LLVM 3.3 with Dragon Egg 3.3 on an x86-64 machine. So far, we have run one SPEC CPU2006 test with the MI scheduler enabled using the option -fplugin-arg-dragonegg-llvm-option='-enable-misched:true' with -O3.

...SNDBUF = 65535 socket option SO_RCVBUF = 65535 socket option SO_SNDLOWAT = 1 socket option SO_RCVLOWAT = 1 socket option SO_SNDTIMEO = 0 socket option SO_RCVTIMEO = 0 Sending a packet of len 50 to (10.1.1.255) on port 137 read_udp_socket: lastip 10.1.1.1 lastport 137 read: 68 parse_nmb: packet id = 7660 Received a packet of len 68 from (10.1.1.1) port 137 nmb packet from 10.1.1.1(137) header: id=7660 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=IOWATRIBE<1b&gt...

Thank you for the answers! We are currently trying to test the MI scheduler. We are using LLVM 3.3 with Dragon Egg 3.3 on an x86-64 machine. So far, we have run one SPEC CPU2006 test with the MI scheduler enabled using the option -fplugin-arg-dragonegg-llvm-option='-enable-misched:true' with -O3. This enables the machine scheduler in addition to the SD scheduler. We have verified this by

...checking for putprpwnam configure:7287: checking for set_auth_parameters in -lsecurity configure:7336: checking for set_auth_parameters configure:7448: checking for set_auth_parameters in -lsec configure:7497: checking for set_auth_parameters configure:7611: checking for getspnam in -lgen configure:7660: checking for getspnam configure:7773: checking for getspnam in -lsecurity configure:7822: checking for getspnam configure:7934: checking for getspnam in -lsec configure:7983: checking for getspnam configure:8096: checking for bigcrypt in -lsecurity configure:8145: checking for bigcrypt configure:8...