回复：Linux 更新
首次公开证据
打开首次公开证据查看 1 个交叉存档
来源说明
Published on GitHub in February 2024 as part of Martti Malmi's testimony in the COPA v. Wright trial
第一眼看，bitcoinshop.com 更好。bitcoinexchange.com 可能比 bitcoinx.com 更好。
搜索域名时要小心，很多服务会抢先注册你搜索的域名。甚至 Network Solutions 也会这样，尽管他们说，如果你使用的是他们的 whois 页面而不是主页，就不会这么做。唯一安全的地方是 http://www.internic.com/whois.html
也许使用真实姓名更好。
还有一个名称问题：我一直在想交易所服务的名字，想出了 Bitcoin X (bitcoinx.com) 和 Bitcoin Shop (bitcoinshop.com)。你觉得哪个更好？
那我最好安装 64 位版本。我猜这与 64 位 Linux 上的 32 位 Berkeley DB 有关。
顺便，在功能列表的署名等地方，你希望我称你为 sirius-m 还是 Martti Malmi？我觉得大多数项目为了保持一致都会使用真实姓名。
程序几次因为 debug.log 中同样的 Db::close 错误而终止。Db.log 中有：
close: Bad file descriptor blkindex.dat: Bad file descriptor
我运行的是 64 位 Ubuntu 发行版。
现在唯一的问题是他遇到的 DB 异常。
EXCEPTION: 11DbException Db::open: Bad file descriptor bitcoin in ThreadMessageHandler()
EXCEPTION: 11DbException Db::close: Bad file descriptor bitcoin in ThreadMessageHandler()
我原以为那是 Wine 的问题，但他在 Linux 上也遇到了完全相同的问题。他尝试把 datadir 移到另一块硬盘上，没有帮助。我从来没遇到过。我正在运行一个不断生成大量活动和数据库访问的压力测试，但始终没遇到它。
他有 64 位 Ubuntu，而我有 32 位，所以我假设这就是区别。你的 Linux 机器是 64 位还是 32 位？你曾经遇到过 DB 异常吗？（也看看 db.log。）既然 test5 已经修复僵尸问题，你能开始在自己的 Linux 机器上运行它吗？我们需要第三票，才能更好地判断到底是什么问题。
DB 异常没有被捕获，所以如果你遇到它，程序就会停止。
顺便，zetaboards 坚持显示“Member #”，所以你最好尽快注册并抢一个好的账号编号。
英文原文
展开英文原文
At first glance, bitcoinshop.com looks better. bitcoinexchange.com might be better than bitcoinx.com.
Be careful where you search domain names, many will front-run you. Even network solutions, although they've said they won't if you use their whois page not the homepage. The only safe place is http://www.internic.com/whois.html
Perhaps the real name is better.
Another name question: I've been thinking of a name for the exchange service, and I came up with Bitcoin X (bitcoinx.com) and Bitcoin Shop (bitcoinshop.com). Which one do you find better?
I'd better install 64-bit then. I imagine it's something about the 32-bit version of Berkeley DB on 64-bit Linux.
BTW, in things like the feature list credits, do you want me to refer to you as sirius-m or Martti Malmi? I think most projects go by real names for consistency.
The program terminated a few times with the same error in debug.log from Db::close. Db.log has:
close: Bad file descriptor blkindex.dat: Bad file descriptor
I'm running a 64-bit Ubuntu distribution.
The only problem now is the DB exceptions he's getting.
EXCEPTION: 11DbException Db::open: Bad file descriptor bitcoin in ThreadMessageHandler()
EXCEPTION: 11DbException Db::close: Bad file descriptor bitcoin in ThreadMessageHandler()
I had expected those to be a Wine problem, but he's getting them on Linux just the same. He tried moving the datadir to a different drive, no help. I've never gotten them. I'm running a stress test that continuously generates a lot of activity and DB access and never got it.
He has Ubuntu 64-bit and I have 32-bit, so I'm assuming that's the difference. Is your Linux machine 64-bit or 32-bit? Have you ever had a DB exception? (see db.log also) Now that the zombie problem is fixed in test5, could you start running it on your Linux machine? We could use a 3rd vote to get a better idea of what we're dealing with here. The DB exception is uncaught, so it'll stop the program if you get it.
BTW, zetaboards insists on displaying "Member #", so you better sign up soon and grab a good account number.