similar to: (no subject)

thank you very much for you all. I will try your suggestion ,thx. =20 Best Regards --------------------------------------------- yhhuang =BB=C6=D3=C2=BB=D4 Server Dept. TeleNav Shanghai Inc. Tel:(21)6337 2220 ext 8651 www.telenav.com -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: Wayne Davison [mailto:wayned@samba.org]=20 =B7=A2=CB=CD=CA=B1=BC=E4: 2006=C4=EA3=D4=C26=C8=D5 23:46

I want to call rsync from java webserver in Linux. situation as below: source directory: 001.doc 002.doc /D01/001.doc /D01/002.doc /D01/D11/001.doc /D02/001.doc destination directory: 001.doc 003.doc 004.doc /D01/001.doc /D01/003.doc /D01/004.doc /D01/D11/003.doc /D02/003.doc now, I want to only delete /003.doc when synchronization, no add, no update, This exclude works: rsync -avzu

hi,all, I have a question about how to distinguish local add and remote delete? hope to get answer from any of you, thank you in advanced. how to distinguish local add and remote delete: Local is machine A, Rsync client, remote is machine B, Rsync server. In our application, A and B are load balance and have same import. file changes may happend in machin A or machine B. So each time, A

what is generator hang? when did this situation happend? thank you. =20 Best Regards --------------------------------------------- yhhuang =BB=C6=D3=C2=BB=D4 Server Dept. TeleNav Shanghai Inc. Tel:(21)6337 2220 ext 8651 www.telenav.com -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: rsync-bounces+yhhuang=3Dtelenav.cn@lists.samba.org =

¶¼Êа×ÁìµÄºÃ¶«¶«---ɽÎÌÇàÅÆϵÁÐÒûÁÏ ¹óÖÝɽÎÌÇà±£½¡ÒûÁϳ§¾àÖøÃûµÄ¹ú¼Ò¼¶·ç¾°Çø--ÐËÒåÂíÁëºÓÏ¿¹È¶þ¹«À¾àÄÏÀ¥Ìú·ÐËÒåվʮ¶þ¹«À¹óÑôÖÁÐËÒ幫·¾­³§¶ø¹ý£¬ÀëÔÆÄÏÀ¥Ã÷¡¢¹ãÎ÷°ÙÉ«¡¢¹óÖݹóÑô¾ù300¶à¹«ÀµØ´¦µá¡¢¹ð¡¢Ç­ÈýÊ¡½áºÏ²¿¡£ÕâÀïɽÇåË®Ð㣬»·¾³ÓÄÑÅ£¬ÎÞ¹¤ÒµÎÛȾ¡£È«³§Ö°¹¤½ü°ÙÈË£¬Óгõ¡¢ÖС¢¸ß¼¶Ö°³ÆÕß10¶àÈË£¬´óÖÐרÉúÕ¼70%ÒÔÉÏ¡£

µÚÎå½ì±±¾©¡°¹ú¼ÊÖÜ¡±³ÏÑûÄúµÄ(¹«Ë¾¡¢ÆóÒµ)²Î¼Ó -- Öйú±±¾©¹ú¼Ê¿Æ¼¼²©ÀÀ»áôßÖйú±±¾©¸ßм¼Êõ²úÒµ¹ú¼ÊÖÜ ¡°ÊÀ½ç500Ç¿CEOÓëÖйú¶¥¼¶ÆóÒµÊ×ÄÔÂÛ̳¡± »áÒé˵Ã÷£º ¾­ÖлªÈËÃñ¹²ºÍ¹ú¹úÎñÔºÅú×¼£¬ ÖлªÈËÃñ¹²ºÍ¹ú¿Æѧ¼¼Êõ²¿¡¢Í⾭󲿡¢½ÌÓý²¿¡¢ÐÅÏ¢²úÒµ²¿¡¢Öйú¹ú¼ÊóÒ×´Ù½øίԱ»á¡¢¹ú¼Ò֪ʶ²úȨ¾ÖºÍ±±¾©ÊÐÈËÃñÕþ¸®¹²Í¬Ö÷°ì£¬ ±±¾©ÊÐó´Ù»á³Ð°ìµÄ¡ª¡ªµÚÎå½ìÖйú±±¾©¸ßм¼Êõ²úÒµ¹ú¼ÊÖÜ(ÒÔϼò³Æ¿Æ²©»á(¹ú¼ÊÖÜ)£¬

µÚÎå½ì±±¾©¡°¹ú¼ÊÖÜ¡±³ÏÑûÄúµÄ(¹«Ë¾¡¢ÆóÒµ)²Î¼Ó -- Öйú±±¾©¹ú¼Ê¿Æ¼¼²©ÀÀ»áôßÖйú±±¾©¸ßм¼Êõ²úÒµ¹ú¼ÊÖÜ ¡°ÊÀ½ç500Ç¿CEOÓëÖйú¶¥¼¶ÆóÒµÊ×ÄÔÂÛ̳¡± »áÒé˵Ã÷£º ¾­ÖлªÈËÃñ¹²ºÍ¹ú¹úÎñÔºÅú×¼£¬ ÖлªÈËÃñ¹²ºÍ¹ú¿Æѧ¼¼Êõ²¿¡¢Í⾭󲿡¢½ÌÓý²¿¡¢ÐÅÏ¢²úÒµ²¿¡¢Öйú¹ú¼ÊóÒ×´Ù½øίԱ»á¡¢¹ú¼Ò֪ʶ²úȨ¾ÖºÍ±±¾©ÊÐÈËÃñÕþ¸®¹²Í¬Ö÷°ì£¬ ±±¾©ÊÐó´Ù»á³Ð°ìµÄ¡ª¡ªµÚÎå½ìÖйú±±¾©¸ßм¼Êõ²úÒµ¹ú¼ÊÖÜ(ÒÔϼò³Æ¿Æ²©»á(¹ú¼ÊÖÜ)£¬

Hi, Opus team I'm Huang Hao and trouble you again. When I used the OpusRepacketizer as Jean-Marc mentioned, I got a result (maybe problem I'm not sure) that perplexes me, please give me some comments. The result be described as below: First(all init which are needed I have done), I used opus_encode() to get the encoded data successfully. The encoder control parameters are set: VBR=0,

ÈÈÃŵÄѧ¿Æ ȨÍþµÄ»ú¹¹ Ò»Á÷µÄר¼Ò ×îеÄÄÚÈÝ Áé»îµÄÊÚ¿Î »ªÖпƼ¼´óѧ½¯ÊÏ»ù½ð¹¤ÒµÅàѵÖÐÐÄ ±±¾©ÏÖ´ú׿Խ¹ÜÀí¼¼Êõ½»Á÷ÖÐÐÄ ÔÚÖ°ÈËÔ±ÏîÄ¿¹ÜÀíÑо¿Éú¿Î³Ì½øÐÞ°à ÕÐ Éú ¼ò Õ һ¡¢ÏîÄ¿¹ÜÀíÑо¿Éú¿Î³Ì½øÐÞ°àµÄ¿ªÉè±³¾°

From: Minfei Huang <mnghuan at gmail.com> We do a lot of memory allocation in function init_vq, and don't handle the allocation failure properly. Then this function will return 0, although initialization fails due to lacking memory. At that moment, kernel will panic in guest machine, if virtio is used to drive disk. To fix this bug, we should take care of allocation failure, and return

From: Minfei Huang <mnghuan at gmail.com> We do a lot of memory allocation in function init_vq, and don't handle the allocation failure properly. Then this function will return 0, although initialization fails due to lacking memory. At that moment, kernel will panic in guest machine, if virtio is used to drive disk. To fix this bug, we should take care of allocation failure, and return

ÎÒ¹«Ë¾ÏµÍâóÆóÒµ£¬ÓÐÒâÀ©´ó¾­Óª¹æÄ££¬ÏëÔÚ¹óµØÑ°ÕÒºÏ×÷»ï°é£¬Ìؽ«´Ë¼ÛÄ¿±íÌṩ¸øÄú·½²Î¿¼£¬ÎÒ¹«Ë¾±£Ö¤²úƷΪȫÐÂÔ­×°Èý¸öÔ°ü»»Ò»Äê°üÐÞÈý°ü£¬±£Ö¤ÐÅÓþ£¬»õµ½¸¶¿î £¬²»ÏêÊÂÒËÄú¿ÉÀ´ÈËÀ´µç´¹Ñ¯£¡ÈçÓдòÈÅ£¬Çë¶à°üº­£¡£¡£¡ ÁªÏµÈË£º¹ù½õºê ÁªÏµµç»°£º(0)13859713911 ¹«Ë¾£ºÌ¨Íą̊±±ºè´óÆóÒµÉÌó¹«Ë¾ Ò»¡¢µçÄÔÅä¼þ (ÈËÃñ±Ò) 1.cpu InteI p4 2G/1.8G/1.7G(Socket478) £¤ 500/420/390Ôª InteI p4 1.6G/1.5G/1.4G(Socket478) £¤

Untitled Document Áö¿ªÀ» °ü¸®ÇÏ½Ç ÁÖºÎÆÀÀåÀ» ÃʺùÇÕ´Ï´Ù ! ´ç»ç´Â ±èÄ¡³ÃÀå°í Àü¹®À¯Åë¾÷ü·Î¼­ °¢ Áö¿ªÀ» °ü¸®ÇÏ½Ç ÁÖºÎÆÀÀå´ÔÀ» ¸ð½Ê´Ï´Ù ÇöÀç ±èÄ¡³ÃÀå°í º¸±ÞÀ²Àº ´ëµµ½Ã°¡ 25%,Áö¹æÀº 15% ¼öÁØ¿¡ ºÒ°ú ÇÏÁö¸¸ À̹ø³âµµ ºÎÅÍ ¸¹Àº ÆǸÅÁõ°¡·Î ÀÎÇØ ³â°£ ÆǸŴë¼ö°¡ ÀÌ¹Ì TV³ª ³ÃÀå°í¿¡ À°¹ÚÇÏ°í ÀÖÀ¸¸ç ¾ÕÀ¸·Î ´õ¿í ´õ ¸¹Àº ÁֺεéÀÌ ±èÄ¡³ÃÀå°í¸¦ ±¸ÀÔ ÇÒ °ÍÀ¸·Î ¿¹»óµÇ°í ÀÖ½À´Ï´Ù.

Untitled Document Áö¿ªÀ» °ü¸®ÇÏ½Ç ÁÖºÎÆÀÀåÀ» ÃʺùÇÕ´Ï´Ù ! ´ç»ç´Â ±èÄ¡³ÃÀå°í Àü¹®À¯Åë¾÷ü·Î¼­ °¢ Áö¿ªÀ» °ü¸®ÇÏ½Ç ÁÖºÎÆÀÀå´ÔÀ» ¸ð½Ê´Ï´Ù ÇöÀç ±èÄ¡³ÃÀå°í º¸±ÞÀ²Àº ´ëµµ½Ã°¡ 25%,Áö¹æÀº 15% ¼öÁØ¿¡ ºÒ°ú ÇÏÁö¸¸ À̹ø³âµµ ºÎÅÍ ¸¹Àº ÆǸÅÁõ°¡·Î ÀÎÇØ ³â°£ ÆǸŴë¼ö°¡ ÀÌ¹Ì TV³ª ³ÃÀå°í¿¡ À°¹ÚÇÏ°í ÀÖÀ¸¸ç ¾ÕÀ¸·Î ´õ¿í ´õ ¸¹Àº ÁֺεéÀÌ ±èÄ¡³ÃÀå°í¸¦ ±¸ÀÔ ÇÒ °ÍÀ¸·Î ¿¹»óµÇ°í ÀÖ½À´Ï´Ù.

On Tue, 19 Jul 2016 12:32:42 +0800 Minfei Huang <mnfhuang at gmail.com> wrote: > From: Minfei Huang <mnghuan at gmail.com> > > We do a lot of memory allocation in function init_vq, and don't handle > the allocation failure properly. Then this function will return 0, > although initialization fails due to lacking memory. At that moment, > kernel will panic in

On Tue, Jul 19, 2016 at 5:32 AM, Minfei Huang <mnfhuang at gmail.com> wrote: > From: Minfei Huang <mnghuan at gmail.com> > > We do a lot of memory allocation in function init_vq, and don't handle > the allocation failure properly. Then this function will return 0, > although initialization fails due to lacking memory. At that moment, > kernel will panic in guest

On Mon, 18 Jul 2016 22:01:29 +0800 Minfei Huang <mnfhuang at gmail.com> wrote: > We do a lot of memory allocation in function init_vq, and don't handle > the allocation failure properly. Then this function will return 0, > although initialization fails due to lacking memory. At that moment, > kernel will panic in guest machine, if virtio is used to drive disk. > > To

Dear r-help, ¬°¤°»ò¤@¯ë¤H¹ï¤k¥Íªº¨èªO¦L¶H´N¬O·Å¬X¡Bµ½Åé¤H·N¡B»y¨¥¯à¤O±j¡F ¦Ó¬Û¹ï¦a»{¬°¨k¥Í«h¤ñ¸û«i´±¡B½Ä°Ê¡B¦n¦â¡BªÅ¶¡·P¡B¤è¦V·P¨Î¡H §A¬O§_´¿¸gÃhºÃ¹L¡A ³o¨Ç¨èªO¦L¶H¤¤ªº¨â©Ê®t²§¨s³º¬O¨k¤k¨â©Ê¦b¥Í²zµo®i¤W»P¥Í­Ñ¨Óªº¤£¦P¿ò¶Ç¦]¤l©Ò³y¦¨ªº¡A ©Î¬O«á¤Ñªº±Ð¾i»P¤å¤Æ©Ò«¬¶ì¥X¨Óªº¡H ¦Ó¤£¦P¤å¤Æ¤¤¹ï¨k¤l®ð·§»P¤k©Ê¯S½è©Î¦h©Î¤Öªº±j½Õ»P­«µø¡A ¤S©M³o¼Ëªº¨èªO¦L¶H¦³¤°»òÃö«Y©O¡H

We do a lot of memory allocation in function init_vq, and don't handle the allocation failure properly. Then this function will return 0, although initialization fails due to lacking memory. At that moment, kernel will panic in guest machine, if virtio is used to drive disk. To fix this bug, we should take care of allocation failure, and return correct value to let caller know what happen.

We do a lot of memory allocation in function init_vq, and don't handle the allocation failure properly. Then this function will return 0, although initialization fails due to lacking memory. At that moment, kernel will panic in guest machine, if virtio is used to drive disk. To fix this bug, we should take care of allocation failure, and return correct value to let caller know what happen.