尝试使用 locate 命令定位ioncube程序的位置：
locate ioncube
输出：
-bash: locate: command not found
因为需要安装mlocate相应的包：
yum -y install mlocate
再次执行 locate 命令，输出：
locate: can not stat () `/var/lib/mlocate/mlocate.db': No such file or directory
解决的办法是更新库：
updatedb
再次执行 locate 命令，输出：
/usr/local/ioncube ... /usr/local/ioncube/ioncube_loader_lin_5.6.so /usr/local/ioncube/ioncube_loader_lin_5.6_ts.so /usr/local/ioncube/loader-wizard.php
【介绍】
INDY的全名是Internet Direct（也叫Winshoes），它是一套功能丰富、使用方便、开源免费的INTERNET控件集，它支持大部分流行的Internet协议，包括 TCP、UDP、 DNS、ICMP、FINGER、FTP、GOPHER、HTTP、POP3、SMTP、TELNET、WHOIS等，支持BASE64、MD2、 MD4、MD5等编解码，提供INTERNET流行协议的客户端和服务器控件。INDY控件集的客户端和服务器控件都有完整、详细的源代码例程和帮助文 件，用户可以根据这些例子，简单方便快速的建造各种服务器程序，例如WEB服务器、 TELNET服务器、IRC服务器、TCP、UDP服务器等，而这些服务器都是支持多线程的。用户也可以很简单的编写出各种客户端程序，例如EMAIL、FINGER、FTP、PING、TELNET等。著名的OICQ使用的协议是UDP，有了INDY你可以使用UDP服务器和UDP客户端写出一个和 OICQ较劲的东东来。
INDY是完全基于SOCKET阻塞工作模式的开发库，现在已经支持BORLAND Delphi、C++ BUIDER和最新的Kylix（LINUX里的Delphi）等开发平台。
an I use Indy in my shareware/commercial applications?
我能在共享软件或商业软件中使用Indy组件吗？
Yes, you may use Indy in your commercial or shareware application if you follow the Indy license. We are aware of several commercial programs and even a commercial component set that uses Indy.
可以，只要您遵守Indy组件的协议，您就能在您的商业软件或共享软件中使用Indy组件。我们已经知道一些商业程序甚至商业组件集使用Indy组件。
Normally what we ask is you use a “made with Indy” or even the button on the website in an about box or such, and the license text in the docs somewhere. You should display the following copyright notice somewhere in your program such as an About Box, splash screen, or documentation:
通常我们只要求您在您的网站上的“关于”中放置一个按钮或者一个“ made with Indy”标志，并且在文档中放置Indy的协议文档。您必须在您的程序的适当位置（如关于对话框，启动画面或文档中）放置如下的版权声明：
Portions of this software are Copyright (c) 1993 – 2003, Chad Z. Hower (Kudzu) and the Indy Pit Crew – http://www.nevrona.com/Indy/
本软件的一部分的版权属于1993 – 2003, Chad Z. Hower (Kudzu) and the Indy Pit Crew – http://www.nevrona.com/Indy/
【安装】
1，卸载旧版本：
使用Delphi的安装程序来卸载
2，安装Indy新版：Indy Download
[BCB6] INDY 安装讨论
用视频演示的方式介绍如何在 Delphi 2007 下删除 Delphi 自带的 Indy 版本，并安装 Indy 的快照版（既最新版）。这是本人第一次玩视频录像，在解说的过程中有点语无伦次，呵呵，请大家谅解哈！补充一句，貌似我在视频中误删了deployindy.bpl，大家操作的时候请留意，不要删除它。
附上简要安装方法的文字说明：
安装方法
安装前请先确定已经删除旧版本的Indy(包括随Delphi安装的版本)，并删除所有和Indy有关的文件（包括dcu,pas,bpl,dcp等文件）。
解压Indy10.zip到C:\Indy10
目录中（路径为假设地址，您可以根据喜好自己决定解压位置），然后用Delphi打开C:\Indy10\Lib\Computil.dpr，编译，得到 Computil.exe文件。注意，如果您使用的是Delphi6，请确保已经打上了SP2的补丁。然后根据您的Delphi版本，分别执行不同的 bat文件来进行编译。现在假设您装的是Delphi7，请双击C:\Indy10\Lib\Fulld7.bat进行编译（如果您用的是BCB6，请使 用Fullc6.bat编译）。然后会得到C\Indy10\D7目录，这个目录下有编译好的所有dcu和bpl文件。现在打开Delphi,点 Component菜单，选择Install Packages菜单项，点Add按钮，然后把C:\Indy10\D7目录下的， dclIndy*.bpl添加到Design packages列表中。然后点Tools-Environment Options菜单，点 Library选项卡，把C:\Indy10\D7目录加到Library Path中，再把C:\Indy10\Lib\下的所有子目录加到 Browsing Path中，点OK。即完成安装。
Indy 快照版下载地址：http://www.2ccc.com/article.asp?articleid=4100
Indy10 is integrated with Delphi 2007 for Win32. However, you can install the earlier version, Indy 9, from RAD Studio\5.0\Source. Delphi 2007 Readme.
三. Indy组件介绍
6-1 IdTCPClient
6-1-1 属性
6-1-2 BoundIP和BoundPort与Host和Port的不同
6-1-3 方法
6-2 IdTCPServer
6-2-1 属性
6-2-2 如何使用Bindings
6-2-3 示例 117
6-3 IdDayTime和IdDayTimeServer 118
6-3-1 IdDayTime 119
6-3-2 IdDayTimeServer 119
6-4 IdEcho和IdEchoServer 120
6-5 IdTime和IdTimeServer 120
6-6 IdTelnet和IdTelnetServer 122
6-7 IdFinger和IdFingerServer 127
第7章 Indy9中的FTP组件 131
7-1 FTP文件传输协议基本概念 132
7-2 FTP服务器的设计 133
7-2-1 OnUserLogin事件 133
7-2-2 OnListDirectory事件 134
7-2-3 OnChangeDirectory事件 138
7-2-4 OnMakeDirectory事件 140
7-2-5 OnRemoveDirectory事件 141
7-2-6 OnStoreFile事件 142
7-2-7 OnReceiverFile事件 143
7-2-8 OnDeleteFile事件 143
7-2-9 OnGetFileSize事件 145
7-2-10 OnRenameFile事件 145
7-3 ASender介绍 147
7-4 IdFTPServer中的属性 148
7-4-1 AllowAnonymousLogin属性 148
7-4-2 AnonymousAccounts属性 149
7-4-3 AnonymousPassStrictCheck属性 149
7-4-4 EmulateSystem属性 150
7-4-5 MaxConnections属性 150
7-4-6 MaxConnectionReply属性 151
7-4-7 UserAccounts属性 152
第8章 邮件及新闻组件的使用 155
8-1 IdPOP3组件的使用 156
8-1-1 邮件数目 157
8-1-2 邮件标题 157
8-1-3 邮件接收 159
8-2 IdSmtp组件的使用 161
8-2-1 设置邮件服务器 162
8-2-2 连接SMTP服务器 163
8-2-3 断开SMTP服务器 163
8-2-4 填充邮件内容 163
8-2-5 加入邮件附件 164
8-2-6 发送电子邮件 165
8-2-7 更多的内容 165
8-3 什么是新闻组 167
8-3-1 获取新闻组列表 168
8-3-2 取得文章列表 171
8-3-3 得到文章内容 173
8-3-4 IdNNTP的高级内容 176
8-3-5 最后的总结 178
第9章 IdHTTP组件介绍 179
9-1 组件的方法介绍 180
9-1-1 Get方法 180
9-1-2 POST和PUT方法 183
9-1-3 Head方法 187
9-1-4 更多的方法 188
9-2 属性介绍 189
9-2-1 ProtocolVersion属性 190
9-2-2 Host和Port属性 191
9-2-3 Request属性 192
9-2-4 CookieManager属性 194
9-2-5 ProxyParams属性 195
9-3 最后的总结 196
第10章 Indy中的UDP组件 197
10-1 IdUDPClient和IdUDPServer组件 198
10-1-1 发送UDP数据包 200
10-1-2 接收UDP数据包 202
10-2 IdDayTimeUDP和IdDayTimeUDPServer组件 205
10-2-1 设置DayTime服务 205
10-2-2 使用DayTime服务 206
10-3 IdTimeUDP和IdTimeUDPServer组件 207
10-3-1 提供Time服务 207
10-3-2 使用Time服务 208
10-3-3 实现代码中的启示 208
10-4 IdEchoUDP和IdEchoUDPServer组件 209
10-5 最后的总结 210
1. 申请邓白氏
2. 申请 Apple idp账号
3. 添加/管理App
网址：https://itunesconnect.apple.com/
创建证书和描述文件：
网址：https://developer.apple.com/account/ios/certificate/
先生成cer文件：
参考：http://jingyan.baidu.com/article/2f9b480d97678041cb6cc290.html
参考：http://blog.csdn.net/holydancer/article/details/9219333
“有时，一次意外，会打乱所有的计划，人们常常把这次挫折看作人生不幸得源泉，但是，未来是由世人的计划决定的吗？不是的。第一个登上高山之巅的人，可能会在山脚制定一些计划，但事实上让他登顶的是计划吗？不是的。事实是，在他攀登的过程中，会遇到未知的障碍和艰难险阻，每一步他都要为下一步做决定，每走一步，计划改变一次，墨守成规可能会让他跌落深谷。他永远无法根据自己的意愿，改变高山，只能去适应高山，同样的道理，不是也适用于人生吗？若一个人把一次意外、一次挫折当成不幸的源头，而亲手终结了生命中的其他可能性，那这个人一生都无法功成名就，也得不到幸福与安宁。换言之，比起试图改变生活，随机应变，适应变动的环境，才是通往成功与幸福的不二法门。好好想想吧!”
“每当人们面临绝境，他们就向至高之神祈祷，恳求神灵相助渡过难关。但是，这些祈祷的真义究竟是什么，我们可曾想过？祈祷的含义，是将一个人的畏惧，忧愁、决心选择和谋划，置于至高神的支配之下，也就是说，不再忧心自己的举动将会产生何种后果，而是践行正法，将神的意旨视为自己的命运……这不就是祈祷吗？然而，人们真有可能理解至高神的意旨么？他的意旨最终导至我们行动的结果。但如果人们全然弃绝了行动，又算什么祈祷呢？事实是，行动即是人生，不贪求成果，才是真正的祈祷。如果祈祷祝告，会使一个人消极处事，无所作为，那这究竟是祈祷还是投降？好好想想吧！”
参考：https://www.namepros.com/threads/io-is-transitioning-to-affilias-is-this-good-or-bad.1019079/
参考：https://corehub.net/registrypolicies/
.io, .sh, .ac: Transition to Afilias registry system and significant changes
Afilias will be the new technical back-end provider for the Internet Computer
Bureau (ICB Registry). The transition of the registry system for the ccTLDs .io,
.sh and .ac to the Afilias registry system will be processed from June 10 (15:00
UTC) until June 11, 2017 (06:00 UTC).
*As a consequence, the domain life cycle of .io, .sh and .ac will be adjusted to
the standard gTLD life cycle.*
*The main changes in an overview, effective as of June 11:*
* Domain name operations for .io, .sh and .ac domains will be processed
identically to .info domain operations.
* Domain names may be registered and renewed for a period of 1 to 10 years.
* There will be the normal 60-day transfer prohibited status on all new creates.
* After migration to the Afilias registry system, domains upon expiry will be
auto-renewed and the relevant grace period (45 days) will apply. Names that
may have expired but not been deleted from the registry system (prior to the
migration) will be automatically renewed and will remain in Autorenew Grace
Period for 45 days.
* Support of all IDNs that are available at the Afilias registry system.
Info provided by RRPproxy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Piffle I was using the direct nic.io to take advantage of the huge 90 day Redemption Grace Period
Wow, lots of Pros and Cons, not sure if this will be good or bad overall.
Most likely there won’t be a direct nic.io backorder anymore, and MAYBE this means normal people will be able to beat out park.io on drops – that would be nice, yet the direct backorder was cool, except for the zero refund policy.
HOPEFULLY, this will drop the price for registration and renewals.
Right now, I have a few domains I’m still floating in RGP, I will contact nic.io and see what do do with them, my best guess is I will have to renew before the June 10th deadline : bummer :
Anyone with more information please share!
OK I sent support tickets to a few registrars and nic.io direct, here’s some replies
The lack of information and/or decision in these replies is rather weak for me, given the timeline that this is only about three weeks away
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
nic.io
Hi there – I just found out you are transitioning to the Afilias Back End June 10th, 2017
Can you share any more details about this? Like what the prices will be, if there will still be a tiered discount, what happens to the backorder system and what happens to RGP?
What happens to my direct account here also? Thank you – have a super day!
—–
Thanks for contacting us
The prices (and discounts) will be the same.
NEW backorders are likely to stop although pre-existing backorders will he honoured
Direct accounts will move to 101domains (Afilias’ retail arm)
Have a great w/end
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NameCheap
I just found out that the dot IO registry is transitioning to the Afilias Back End and it is scheduled for June 10th, 2017
Your price for dot IO registration renewal and transfer right now is $32.88. Do you know if the change to Affilias will also be affecting the prices of IO? Hopefully they decrease : smile :
https://www.namepros.com/threads/io-is-transitioning-to-affilias-is-this-good-or-bad.1019079/
Afilias Wins Contract to Run Backend Registry Services for .io, .ac and .sh
Thank you – have a super day!
—–
Thank you for contacting Namecheap Customer Support!
Indeed, we are aware of this transition. Regretfully, though, we have not received any details in regards to price change.
Still, please rest assured that once we receive any news, we will make sure to announce it via our Newsletter.
Should you have any other questions or require help, please do not hesitate to let us know.
We are here for you 24/7/365.
Regards, Namecheap Customer Support
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Moniker
[same inquiry as NC above with Monikers prices]
—–
thank you for contacting Moniker Support.
At this moment we do not have any information about any price changes. You could revised this pdf were we keep all of our current prices. If there are any changes we will update this document.
https://www.moniker.com/files/moniker-pricing-aug-2016_mk4.pdf
Should you have any further questions, please do not hesitate to contact us.
Best regards,Your Team @ Moniker.com
usernamex said: ↑
MAYBE this means normal people will be able to beat out park.io on drops
All park.io needs to do is a standard drop-catch over EPP – “normal” people can beat them by buying a back-order. If back-orders are going to get dropped, then this will likely help park.io, unless Afilias randomise their delete times.
nic.io batch delete at 00:30 – so all Park would have to do is fire-off 100s of purchase request around that time – if the name hadn’t yet been deleted they would get a “failed” reply. The first request after the delete would them get a “success” reply – that’s how all drop-catch works.
You normally need a registrar account to use EPP.