首页 \ 问答 \ 无法在Windows上使用rsync方法进行流浪(Can't vagrant up with rsync method on windows)

无法在Windows上使用rsync方法进行流浪(Can't vagrant up with rsync method on windows)

 一旦我运行vagrant并在配置类型中使用rsync方法，我得到了以下错误  
There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /e/virtual-boxes/scotchbox/
Guest path: /var/www
Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'E:/virtual-boxes/scotchbox/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ --exclude .git/ /e/virtual-boxes/scotchbox/ vagrant@127.0.0.1:/var/www
Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
dup() in/out/err failed
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.1]

I got the below errors once I run vagrant up and using rsync method in config type 
There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /e/virtual-boxes/scotchbox/
Guest path: /var/www
Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'E:/virtual-boxes/scotchbox/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ --exclude .git/ /e/virtual-boxes/scotchbox/ vagrant@127.0.0.1:/var/www
Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
dup() in/out/err failed
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.1]

原文：https://stackoverflow.com/questions/36251364

更新时间：2022-09-14 15:09

最满意答案

 经过很多痛苦之后，我决定不使用iFrame重新设计。 我认为iFrame是最好的方式然后意识到我错了，至少在我目前的理解水平上。 但是，使用此方法，我可以从fancyBox弹出窗口成功调用警报：  
 http://jsfiddle.net/nicorellius/d4KVs/  
 我想我也可以在这里使用我现有的验证。  
 这是更改的HTML：  
<a href="#test" class="fancy-popup">fancy link</a>
 
 我把HTML放在一个地方，并使用现有的fancyBox技术引用它。  
 但是，我并没有完全放弃。 我一直在摆弄它并找到了使用iFrame的解决方案。 不确定我做了什么，但我设置了原始计划，并使用了脚本：  
    function alert_me() {
        $.fancybox.inner.find('iframe').contents().find(
            'input.click-me').click(function() {
                alert("fancybox has been foiled!!!");
        });
    }
 
 现在，警报框在iFrame fancyBox中弹出。  
 这个问题的解决方案是：它可能仅限于我所在的同一个域，因此在生产中它可能无法工作。 我跑了一个快速测试，似乎跨域工作，但我觉得它将来会给我带来麻烦...... 

After a lot of pain, I decided to rework this without using an iFrame. I thought the iFrame was the best way to go but then realized I was wrong, at least at my current level of understanding. However, with this method, I can successfully call the alert from the fancyBox popup: 
http://jsfiddle.net/nicorellius/d4KVs/ 
I think I can use my existing validation here too. 
Here is HTML that changed: 
<a href="#test" class="fancy-popup">fancy link</a>
 
I put the HTML in one place and referenced it using existing fancyBox techniques. 
I didn't give up all the way, however. I kept on fiddling with it and found a solution using the iFrame. Not sure exactly what I did, but I set up original plan, and used the script: 
    function alert_me() {
        $.fancybox.inner.find('iframe').contents().find(
            'input.click-me').click(function() {
                alert("fancybox has been foiled!!!");
        });
    }
 
and now the alert box pops up within the iFrame fancyBox. 
The thing is with this solution is: it may be limited to the same domain I'm on, so in production it probably wont work. I ran a quick test and it seems to work cross domain but I have a feeling it'll cause me trouble in the future...

无法在Windows上使用rsync方法进行流浪(Can't vagrant up with rsync method on windows)

最满意答案

相关问答

Javascript和jQuery（Fancybox）的问题(Javascript and jQuery (Fancybox) question)[2023-10-18]

作为一个孩子打开fancybox（iframe）？(Open fancybox(iframe) as a child?)[2022-12-20]

用延迟打开fancybox iframe(Open fancybox iframe with delay)[2023-12-06]

从Fancybox弹出窗口中调用警报功能 - iFrame和同源策略(Call Alert Function from within Fancybox Popup Window - iFrame and Same Origin Policy)[2023-12-13]

Fancybox使用什么参数，以便在自动窗口中打开IFRAME？(What parameter to use for Fancybox so IFRAME opens in an autosized window?)[2022-03-11]

fancybox不同的关闭功能(fancybox different close functions)[2022-04-27]

Fancybox视频弹出窗口没有显示(Fancybox video popup not showed)[2023-03-20]

如何克服iframe中的同源策略？(How to overcome same-origin-policy from iframe?)[2021-09-13]

如何修复弹出窗口iframe以避免相同的域策略？(How do I fix popup iframe to avoid same domain policy?)[2024-02-02]

Fancybox popup很小(Fancybox popup is to small)[2022-01-23]