search for: csrc

...Blocking entrylks failed. [2017-12-21 13:56:01.594350] W [MSGID: 108019] [afr-lk-common.c:1064:afr_log_entry_locks_failure] 0-g_sitework2-replicate-4: Unable to obtain sufficient blocking entry locks on at least one child while attempting RMDIR on {pgfid:23558c59-87e5-4e90-a610-8a47ec08b27c, name:csrc}. [2017-12-21 13:56:01.594648] I [MSGID: 108019] [afr-transaction.c:1903:afr_post_blocking_entrylk_cbk] 0-g_sitework2-replicate-4: Blocking entrylks failed. [2017-12-21 13:56:01.594790] W [MSGID: 112032] [nfs3.c:3713:nfs3svc_rmdir_cbk] 0-nfs: df521f4d: <gfid:23558c59-87e5-4e90-a610-8a47ec08b27...

...t; > [2017-12-21 13:56:01.594350] W [MSGID: 108019] > [afr-lk-common.c:1064:afr_log_entry_locks_failure] > 0-g_sitework2-replicate-4: Unable to obtain sufficient blocking entry locks > on at least one child while attempting RMDIR on {pgfid:23558c59-87e5-4e90-a610-8a47ec08b27c, > name:csrc}. > > [2017-12-21 13:56:01.594648] I [MSGID: 108019] [afr-transaction.c:1903:afr_post_blocking_entrylk_cbk] > 0-g_sitework2-replicate-4: Blocking entrylks failed. > > [2017-12-21 13:56:01.594790] W [MSGID: 112032] [nfs3.c:3713:nfs3svc_rmdir_cbk] > 0-nfs: df521f4d: <gfid:23558c5...

...-21 13:56:01.594350] W [MSGID: 108019] >> [afr-lk-common.c:1064:afr_log_entry_locks_failure] >> 0-g_sitework2-replicate-4: Unable to obtain sufficient blocking entry locks >> on at least one child while attempting RMDIR on >> {pgfid:23558c59-87e5-4e90-a610-8a47ec08b27c, name:csrc}. >> >> [2017-12-21 13:56:01.594648] I [MSGID: 108019] >> [afr-transaction.c:1903:afr_post_blocking_entrylk_cbk] >> 0-g_sitework2-replicate-4: Blocking entrylks failed. >> >> [2017-12-21 13:56:01.594790] W [MSGID: 112032] >> [nfs3.c:3713:nfs3svc_rmdir_cbk]...

...exist (Orange Book = > 5200.28-STD, aka DoD Trusted Computer System Evaluation Criteria). > Should anyone care to learn from the Rainbow Books, they are available from the United States of America (USA) National Institute of Standards and Technology (NIST) Computer Security Resource Center (CSRC) Selected Historical Computer Security Papers, http://csrc.nist.gov/publications/secpubs/ There is a caveat however, "The Rainbow Series of Department of Defense standards is outdated, out of print, and provided here for historical purposes ONLY." I imagine the CSRC believes some of their...

...the client command like ssh-keygen either. My questions are: 1. Does OpenSSH support FIPS mode? 2. Or does OpenSSH support with OpenSSL FIPS modules? 3. Is there a way to re-compile OpenSSH by turning on/off some flags to make it FIPS complaint? 4. Does the RedHat OpenSSH FIPS modules ( http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1791.pdf) also open sourced to the OpenSSH community? Thanks.

Now that OpenSSL has received FIPS 140-2 certification, does anyone know if the work started a couple of years ago to allow OpenSSH to use OpenSSL in FIPS mode will be reactivated? Bill

...km4)) + out = calc_P(clk->read(clk, nv_clk_src_hclkm4), core, &divs); + + /* Calculate clock * 2, so shader clock can use it too */ + clock = calc_pll(priv, 0x4028, (core << 1), &N, &M, &P1); + + if (abs(core - out) <= + abs(core - (clock >> 1))) { + priv->csrc = nv_clk_src_hclkm4; + priv->cctrl = divs << 16; + } else { + /* NVCTRL is actually used _after_ NVPOST, and after what we + * call NVPLL. To make matters worse, NVPOST is an integer + * divider instead of a right-shift number. */ + if(P1 > 2) { + P2 = P1 - 2; + P1 = 2; + }...

...km4)) + out = calc_P(clk->read(clk, nv_clk_src_hclkm4), core, &divs); + + /* Calculate clock * 2, so shader clock can use it too */ + clock = calc_pll(priv, 0x4028, (core << 1), &N, &M, &P1); + + if (abs(core - out) <= + abs(core - (clock >> 1))) { + priv->csrc = nv_clk_src_hclkm4; + priv->cctrl = divs << 16; + } else { + /* NVCTRL is actually used _after_ NVPOST, and after what we + * call NVPLL. To make matters worse, NVPOST is an integer + * divider instead of a right-shift number. */ + if(P1 > 2) { + P2 = P1 - 2; + P1 = 2; + }...

...view, we should only add metadata to loads and stores that are inserted due to memory accesses in the source code. Meaning they are due to an array or pointer access. Cheers, Tobi -------------- next part -------------- A non-text attachment was scrubbed... Name: ivdep_t_private.c Type: text/x-csrc Size: 131 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130303/add42a0a/attachment.c> -------------- next part -------------- A non-text attachment was scrubbed... Name: ivdep_t_non-private.c Type: text/x-csrc Size: 130 bytes Desc: not available URL: &...

...ized, but when from other h323 endpoint then all work fine. I thought the cisco does't send DTMF event but in rtp dump I saw strange packet where DTMF should be: RTP Packet: Size: 36 Version: 2 Padding: FALSE Extension: FALSE marker: FALSE timestamp: 476982374Payload: 4 SeqNumber: 19447 CSRC count: 0 SSRC: 94351557 RTP Packet: Size: 136 Version: 2 Padding: FALSE Extension: FALSE marker: TRUE timestamp: 94351557 Payload: 200 SeqNumber: 12 CSRC count: 0 SSRC: 3283075717 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ RTP Packet: Size: 36 Version: 2 Paddi...

...timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | synchronization source (SSRC) identifier | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ | contributing source (CSRC) identifiers | | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ <p> The RTP header begins with an octet of fields (V, P, X, and CC) to support specialized RTP uses (see [8] and [9...

Reclocking of NVAA/NVAC is substantially different from NV50+, enough to justify a separate clock implementation. This code is a forward-port of reclocking code that has been sitting in a branch for a while, and has been tested on my NVAC. Traces show no significant reasons why this shouldn't work on NVAA, but testers are always welcome. And since these are IGPs without dedicated RAM to

...timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | synchronization source (SSRC) identifier | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ | contributing source (CSRC) identifiers | | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ <p> The RTP header begins with an octet of fields (V, P, X, and CC) to support specialized RTP uses (see [4] and [5] fo...

...it seems necessary to _not_ annotate the loads and stores from and to 't'. Only after 't' is moved into a register, the loop is actually parallel on the IR level. Cheers, Tobi -------------- next part -------------- A non-text attachment was scrubbed... Name: test.c Type: text/x-csrc Size: 89 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130302/adb705ea/attachment.c>

...operative becasue the text "executing prg" is in line 90 of wineio.c I dont know how get working my hardware thru wine. Best Regards to all, any clue will be appreciated. Christian -------------- next part -------------- A non-text attachment was scrubbed... Name: wineio.c Type: text/x-csrc Size: 2893 bytes Desc: not available URL: <http://www.winehq.org/pipermail/wine-users/attachments/20160502/9c982a9e/attachment.c>

...timestamp | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | synchronization source (SSRC) identifier | +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ | contributing source (CSRC) identifiers | | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ <p> The RTP header begins with an octet of fields (V, P, X, and CC) to support specialized RTP uses (see [8] and [9...

...| > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | synchronization source (SSRC) identifier | > +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ > | contributing source (CSRC) identifiers | > | ... | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > The RTP header begins with an octet of fields (V, P, X, and CC) to > support specialized RT...

I have put a compile hack in for older distros and pushed it out as syslinux-3.62-pre16; for those who have reported compilation problem on older distros I would greatly appreciate if you could confirm if it works now (it worked for me on a CentOS 3.9 VM.) -hpa

...* Conferencing on Asterisk depends on Zaptel hardware and/or kernel modules for timing; * Lack of built-in STUN support for SIP NAT traversal; * Asterisk doesn't use SpanDSP; * Use of no longer maintained Berkeley DB1 engine as its internal database; * Asterisk doesn't allow CSRC entries in RTP; * Asterisk doesn't have an universal jitterbuffer for use with any channel type; * Asterisk doesn't use POSIX realtime extensions (having dependency with Zaptel timing); We were considering Asterisk as the chosen platform, but after reading this I got a little worr...

...with an .msf extension (e.g. INBOX.msf), which is the index (Mail Summary File) to the mail file. Tell the other program to import mail from the file with no extension. However, in the imap.gmail.com folder INBOX.msf file properties, Type is shown as C source code and MIME type is shown as text/x-csrc and I cannot find the mbox files.... In Evolution: Inbox has type: Mailbox file and is shown as MIME type: application/mbox If someone on the list can point me to where the mbox files for Thunderbird on Linux are located, that will be much appreciated. I do not want to migrate from Evolution t...