Hatena::Grouptech

id:rx7(@namikawa)の技術メモ このページをアンテナに追加 RSSフィード

過去記事一覧 | Main Blog (元RX-7乗りの適当な日々) | SBM (id:rx7のBookmark)

2013/08/23

Error: Unable to execute port: can't read "build.cmd"

| Error: Unable to execute port: can't read "build.cmd" - id:rx7(@namikawa)の技術メモ を含むブックマーク はてなブックマーク - Error: Unable to execute port: can't read "build.cmd" - id:rx7(@namikawa)の技術メモ Error: Unable to execute port: can't read "build.cmd" - id:rx7(@namikawa)の技術メモ のブックマークコメント

手元の環境を一新したついでに、Macportsに舞い戻ってみたのですが、パッケージのインストール時に以下のエラーが出る。

Error: Unable to execute port: can't read "build.cmd": Failed to locate 'make' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it?

こういう場合は、Xcodeを起動し、

[Xcode] - [Preferences] - [Download] - [Component]

から、"Command Line Tools"をインストールすべし。

トラックバック - http://tech.g.hatena.ne.jp/rx7/20130823

2013/08/20

AWS(ap-northeast - Tokyo) to AWS(us-east - Northern Virginia)のtraceroute

| AWS(ap-northeast - Tokyo) to AWS(us-east - Northern Virginia)のtraceroute - id:rx7(@namikawa)の技術メモ を含むブックマーク はてなブックマーク - AWS(ap-northeast - Tokyo) to AWS(us-east - Northern Virginia)のtraceroute - id:rx7(@namikawa)の技術メモ AWS(ap-northeast - Tokyo) to AWS(us-east - Northern Virginia)のtraceroute - id:rx7(@namikawa)の技術メモ のブックマークコメント


メモメモ。

上記エントリを書いたときに、AWS東京リージョンの各ゾーンに立ち上げたインスタンスを使って、

us-eastにあるインスタンスへの経路を調べてみた。そのログ。

もちろん経路は日に日によくなっていくと思うので、あくまで現時点のスナップショットの参考までに。


尚、「ap-northeast-1{a,b,c}」と呼ばれる3つのAvailability Zoneは、アカウントID毎にマッピングが違うので、注意してください。(私のアカウントが指す"ap-northeast-1a"と、貴方のアカウントが指している"ap-northeast-1a"は違うZoneかもしれない。)

↑の詳細は、昔のエントリですが、以下に詳細を書いています。


AWS東京リージョンとBGPピアを確立するとレイテンシはどう変わるか+α - 元RX-7乗りの適当な日々

どうも、ap-northeast-1bとap-northeast-1cについては、大阪のKDDI経由で海を渡っているように見えますね。

ap-northeast-1aは、東京のNTT経由で海を渡っているっぽい。

(今、思えばAS_PATHも出しておけばよかった。)


ap-northeast-1a

$ traceroute -I hootsuite.com
traceroute to hootsuite.com (184.72.95.234), 30 hops max, 60 byte packets
 1  ip-10-156-108-3.ap-northeast-1.compute.internal (10.156.108.3)  0.377 ms  0.483 ms  0.534 ms
 2  ip-10-1-26-9.ap-northeast-1.compute.internal (10.1.26.9)  0.499 ms  0.496 ms  0.705 ms
 3  ec2-175-41-192-20.ap-northeast-1.compute.amazonaws.com (175.41.192.20)  0.483 ms  0.723 ms  0.721 ms
 4  27.0.0.146 (27.0.0.146)  1.605 ms  1.635 ms  1.597 ms
 5  27.0.0.128 (27.0.0.128)  5.609 ms  5.631 ms  5.629 ms
 6  ae-10.r00.tokyjp03.jp.bb.gin.ntt.net (61.213.145.1)  2.236 ms  2.166 ms  2.337 ms
 7  ae-12.r25.tokyjp05.jp.bb.gin.ntt.net (129.250.2.4)  2.445 ms  2.919 ms  3.423 ms
 8  ae-13.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.6.191)  2.210 ms  2.493 ms  2.912 ms
 9  as-1.r20.sttlwa01.us.bb.gin.ntt.net (129.250.4.189)  110.040 ms  109.638 ms  109.528 ms
10  ae-0.r21.sttlwa01.us.bb.gin.ntt.net (129.250.2.54)  98.180 ms  95.605 ms  95.834 ms
11  ae-5.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.181)  178.537 ms  178.883 ms  166.984 ms
12  ae-2.r04.asbnva02.us.bb.gin.ntt.net (129.250.4.207)  180.304 ms ae-2.r00.asbnva02.us.bb.gin.ntt.net (129.250.3.114)  180.557 ms  305.481 ms
13  ae-0.amazon.asbnva02.us.bb.gin.ntt.net (168.143.191.18)  181.180 ms  174.775 ms ae-2.amazon.asbnva02.us.bb.gin.ntt.net (168.143.228.38)  303.935 ms
14  72.21.220.29 (72.21.220.29)  179.761 ms 72.21.220.45 (72.21.220.45)  211.616 ms  211.171 ms
15  205.251.245.65 (205.251.245.65)  209.080 ms  233.459 ms  197.146 ms
16  * * *
17  * * *
18  * * *
19  216.182.224.73 (216.182.224.73)  167.761 ms  164.851 ms  168.619 ms
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  ec2-184-72-95-234.compute-1.amazonaws.com (184.72.95.234)  175.786 ms  167.933 ms  176.793 ms

ap-northeast-1b

$ traceroute -I hootsuite.com
traceroute to hootsuite.com (184.72.95.234), 30 hops max, 60 byte packets
 1  ip-10-160-160-3.ap-northeast-1.compute.internal (10.160.160.3)  0.403 ms  0.483 ms  0.641 ms
 2  ip-10-1-14-13.ap-northeast-1.compute.internal (10.1.14.13)  0.389 ms  0.620 ms  0.643 ms
 3  100.64.28.67 (100.64.28.67)  0.575 ms  0.691 ms  0.799 ms
 4  ec2-175-41-192-214.ap-northeast-1.compute.amazonaws.com (175.41.192.214)  0.619 ms  0.641 ms  0.635 ms
 5  27.0.0.210 (27.0.0.210)  61.510 ms  61.528 ms  61.524 ms
 6  27.0.0.196 (27.0.0.196)  11.319 ms  11.029 ms  11.037 ms
 7  113.157.231.13 (113.157.231.13)  11.600 ms  11.615 ms  11.602 ms
 8  obpjbb206.int-gw.kddi.ne.jp (118.155.199.69)  11.109 ms  11.237 ms  11.228 ms
 9  pajbb002.int-gw.kddi.ne.jp (203.181.100.186)  123.949 ms  123.966 ms  123.870 ms
10  ix-pa9.int-gw.kddi.ne.jp (111.87.3.78)  121.361 ms  121.353 ms  121.339 ms
11  xe-4-2-0.pao10.ip4.tinet.net (77.67.77.25)  125.929 ms  125.938 ms  126.145 ms
12  xe-5-1-0.was10.ip4.tinet.net (141.136.108.198)  205.577 ms  205.601 ms  196.477 ms
13  77.67.108.34 (77.67.108.34)  202.309 ms  202.414 ms  202.332 ms
14  72.21.220.69 (72.21.220.69)  200.366 ms  200.452 ms  200.329 ms
15  205.251.245.65 (205.251.245.65)  192.250 ms  192.317 ms  192.222 ms
16  * * *
17  * * *
18  * * *
19  216.182.224.209 (216.182.224.209)  201.964 ms  201.673 ms  202.144 ms
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  ec2-184-72-95-234.compute-1.amazonaws.com (184.72.95.234)  199.841 ms  200.351 ms  192.572 ms

ap-northeast-1c

$ traceroute -I hootsuite.com
traceroute to hootsuite.com (184.72.95.234), 30 hops max, 60 byte packets
 1  ip-10-118-37-193.ap-northeast-1.compute.internal (10.118.37.193)  0.851 ms  1.153 ms  1.431 ms
 2  100.65.9.15 (100.65.9.15)  0.692 ms  0.726 ms  0.722 ms
 3  100.65.9.38 (100.65.9.38)  0.588 ms  0.822 ms  0.845 ms
 4  100.66.56.1 (100.66.56.1)  0.445 ms  0.531 ms  0.675 ms
 5  100.64.12.75 (100.64.12.75)  0.604 ms  0.729 ms  0.836 ms
 6  ec2-175-41-192-202.ap-northeast-1.compute.amazonaws.com (175.41.192.202)  0.720 ms  0.517 ms  0.691 ms
 7  27.0.0.73 (27.0.0.73)  10.012 ms  9.987 ms  9.961 ms
 8  27.0.0.103 (27.0.0.103)  9.721 ms  9.997 ms  10.014 ms
 9  113.157.231.13 (113.157.231.13)  21.369 ms  21.376 ms  20.814 ms
10  obpjbb206.int-gw.kddi.ne.jp (118.155.199.65)  10.369 ms  10.582 ms  10.594 ms
11  pajbb002.int-gw.kddi.ne.jp (203.181.100.186)  122.456 ms  122.392 ms  122.376 ms
12  ix-pa9.int-gw.kddi.ne.jp (111.87.3.34)  124.511 ms  124.719 ms  124.539 ms
13  xe-4-2-0.pao10.ip4.tinet.net (77.67.77.25)  118.176 ms  117.697 ms  117.849 ms
14  xe-5-1-0.was10.ip4.tinet.net (141.136.108.198)  193.591 ms  193.602 ms  193.617 ms
15  77.67.108.34 (77.67.108.34)  193.447 ms  194.641 ms  194.565 ms
16  72.21.220.69 (72.21.220.69)  187.107 ms  187.193 ms  187.341 ms
17  205.251.245.65 (205.251.245.65)  199.024 ms  198.700 ms  214.925 ms
18  * * *
19  * * *
20  * * *
21  216.182.224.79 (216.182.224.79)  201.972 ms  201.438 ms  201.600 ms
22  * * *
23  * * *
24  * * *
25  ec2-184-72-95-234.compute-1.amazonaws.com (184.72.95.234)  183.568 ms  183.584 ms  183.773 ms
トラックバック - http://tech.g.hatena.ne.jp/rx7/20130820

2013/08/12

Windowsでウインドウが画面外にあって移動させたいとき

| Windowsでウインドウが画面外にあって移動させたいとき - id:rx7(@namikawa)の技術メモ を含むブックマーク はてなブックマーク - Windowsでウインドウが画面外にあって移動させたいとき - id:rx7(@namikawa)の技術メモ Windowsでウインドウが画面外にあって移動させたいとき - id:rx7(@namikawa)の技術メモ のブックマークコメント

[Alt] + [Space]

キーを押した後に、

[M]

を押す!

あとは、表示領域の方へ矢印キーで移動させればOK。

トラックバック - http://tech.g.hatena.ne.jp/rx7/20130812

2013/08/02

arp_announce と arp_ignore

| arp_announce と arp_ignore - id:rx7(@namikawa)の技術メモ を含むブックマーク はてなブックマーク - arp_announce と arp_ignore - id:rx7(@namikawa)の技術メモ arp_announce と arp_ignore - id:rx7(@namikawa)の技術メモ のブックマークコメント

メモ。

arp_announce - INTEGER
	Define different restriction levels for announcing the local
	source IP address from IP packets in ARP requests sent on
	interface:
	0 - (default) Use any local address, configured on any interface
	1 - Try to avoid local addresses that are not in the target's
	subnet for this interface. This mode is useful when target
	hosts reachable via this interface require the source IP
	address in ARP requests to be part of their logical network
	configured on the receiving interface. When we generate the
	request we will check all our subnets that include the
	target IP and will preserve the source address if it is from
	such subnet. If there is no such subnet we select source
	address according to the rules for level 2.
	2 - Always use the best local address for this target.
	In this mode we ignore the source address in the IP packet
	and try to select local address that we prefer for talks with
	the target host. Such local address is selected by looking
	for primary IP addresses on all our subnets on the outgoing
	interface that include the target IP address. If no suitable
	local address is found we select the first local address
	we have on the outgoing interface or on all other interfaces,
	with the hope we will receive reply for our request and
	even sometimes no matter the source IP address we announce.

	The max value from conf/{all,interface}/arp_announce is used.

	Increasing the restriction level gives more chance for
	receiving answer from the resolved target while decreasing
	the level announces more valid sender's information.
arp_ignore - INTEGER
	Define different modes for sending replies in response to
	received ARP requests that resolve local target IP addresses:
	0 - (default): reply for any local target IP address, configured
	on any interface
	1 - reply only if the target IP address is local address
	configured on the incoming interface
	2 - reply only if the target IP address is local address
	configured on the incoming interface and both with the
	sender's IP address are part from same subnet on this interface
	3 - do not reply for local addresses configured with scope host,
	only resolutions for global and link addresses are replied
	4-7 - reserved
	8 - do not reply for all local addresses

	The max value from conf/{all,interface}/arp_ignore is used
	when ARP request is received on the {interface}
トラックバック - http://tech.g.hatena.ne.jp/rx7/20130802