回复：Linux 构建已准备好测试
首次公开证据
打开首次公开证据查看 1 个交叉存档
来源说明
Published on GitHub in February 2024 as part of Martti Malmi's testimony in the COPA v. Wright trial
好的，区块现在已经开始增加了。它们开始增加所需的时间明显比 Windows 版本长。而且我认为它们的增加速度也可能比 Windows 版本慢。你发给我的 Linux 构建版本里是不是启用了调试？区块大约以每秒 15 个的速度增加（我一边看钟一边目测估算）。我没有测量 Windows 版本中区块增加得有多快，但感觉要快得多。
大约过了多久才开始？可能只是你碰巧向其请求数据的节点很慢。启动缓慢与下载速度慢的情况是一致的。
我想看看你当前的 debug.log 文件，试着弄清楚发生了什么。可能只是另一端的连接非常慢，也可能是某个环节出了问题、失败后又重试了。耗时太久可能会让其他用户困惑。
Martti，你运行它时过了多久才开始下载区块，下载速度又有多快？
当我启动 bitcoin 而 bitcoin 端口不可用时，命令行会显示 以下消息。当 bitcoin 端口可用时，我不会看到这些消息。 如果默认端口已被占用，bitcoin 能否选择另一个端口？我的 BitTorrent 客户端有时也会发生同样的事情。当我重新启动它时， 我之前开放的端口已经关闭了。我只要更改端口，它就又开始工作了。 /usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so /usr/lib/gio/modules/libgioremote-volume-monitor.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgioremote-volume-monitor.so /usr/lib/gio/modules/libgiogconf.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgiogconf.so
它已经使用了 SO_REUSEADDR，所以端口关闭后即使处于 TIME_WAIT 状态，它也能绑定该端口。它唯一应该无法绑定的情况，是程序确实已经在运行。务必要避免同时在同一台机器上运行两个比特币程序副本，因为它们会同时修改数据库。完全没有必要在一台机器上运行两个副本，因为新币生成现在会自动使用多个处理器。
我不确定那些 lib 错误是什么，我会搜索一下。
英文原文
展开英文原文
Ok, blocks have now started to increase. It definitely takes longer for them to start increasing than with the Windows version. Also, I think they might be increasing at a slower rate than in with the Windows version. Is there perhaps debugging enabled in the Linux build that you sent me? Block are increasing at about 15 blocks per second (eyeball estimate while looking at a clock). I didn't time how fast they increased in the Windows version, but it seems like it was much faster.
About how long did it take to start? It could be the node that you happened to request from is slow. The slow start is consistent with the slow download speed.
I'd like to look at your current debug.log file and try to understand what's going. It might just be a really slow connection on the other side, or maybe something's wrong and failed and retried. Taking too long could confuse other users.
Martti, how long did it take to start downloading blocks when you ran it, and how fast did it download?
When I launch bitcoin and the bitcoin port is not available, I get the following messages to the command line. I don't get those messages when the bitcoin port is available. Would it be possible for bitcoin to pick another port if the default port is taken? The same think sometimes happens to me with my BitTorrent client. When I restart it, my previously open port is closed. All I have to do is change the port and it starts working again. /usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so /usr/lib/gio/modules/libgioremote-volume-monitor.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgioremote-volume-monitor.so /usr/lib/gio/modules/libgiogconf.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgiogconf.so
It already uses SO_REUSEADDR so it can bind to the port if it's in TIME_WAIT state after being closed. The only time it should fail to bind is when the program really is already running. It's important that two copies of Bitcoin not run on the same machine at once because they would be modifying the database at the same time. There is never any need to run two on one machine as coin generation will now use multiple processors automatically.
I'm not sure what those lib errors are, I'll do some searching.