Views: 75
$ sudo yum install inotify-tools 読み込んだプラグイン:priorities, update-motd, upgrade-helper
One of the configured repositories failed (不明),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
$ sudo -s
# yum clean all --enablerepo=*; yum update --disablerepo=epel
読み込んだプラグイン:priorities, update-motd, upgrade-helper
リポジトリーを清掃しています: amzn-main amzn-main-debuginfo amzn-main-source
...: amzn-nosrc amzn-preview amzn-preview-debuginfo amzn-preview-source
...: amzn-updates amzn-updates-debuginfo amzn-updates-source epel
...: epel-debuginfo epel-source epel-testing epel-testing-debuginfo
...: epel-testing-source
Cleaning up everything
読み込んだプラグイン:priorities, update-motd, upgrade-helper
amzn-main | 2.1 kB 00:00
amzn-updates | 2.5 kB 00:00
(1/5): amzn-main/latest/group_gz | 4.4 kB 00:00
(2/5): amzn-updates/latest/group_gz | 4.4 kB 00:00
(3/5): amzn-updates/latest/primary_db | 3.0 MB 00:00
(4/5): amzn-main/latest/primary_db | 4.0 MB 00:00
(5/5): amzn-updates/latest/updateinfo | 641 kB 00:00
No packages marked for update
# exit
exit
$ sudo yum install inotify-tools
読み込んだプラグイン:priorities, update-motd, upgrade-helper
epel/x86_64/metalink | 9.4 kB 00:00
epel | 4.7 kB 00:00
(1/3): epel/x86_64/group_gz | 74 kB 00:00
(2/3): epel/x86_64/primary_db | 6.1 MB 00:00
(3/3): epel/x86_64/updateinfo | 789 kB 00:00
1073 packages excluded due to repository priority protections
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ inotify-tools.x86_64 0:3.14-2.el6 を インストール
--> 依存性解決を終了しました。
依存性を解決しました
================================================================================
Package アーキテクチャー
バージョン リポジトリー 容量
================================================================================
インストール中:
inotify-tools x86_64 3.14-2.el6 epel 46 k
トランザクションの要約
================================================================================
インストール 1 パッケージ
総ダウンロード容量: 46 k
インストール容量: 104 k
Is this ok [y/d/N]: y
Downloading packages:
警告: /var/cache/yum/x86_64/latest/epel/packages/inotify-tools-3.14-2.el6.x86_64.rpm: ヘッダー V3 RSA/SHA256 Signature、鍵 ID 0608b895: NOKEY
inotify-tools-3.14-2.el6.x86_64.rpm の公開鍵がインストールされていません
inotify-tools-3.14-2.el6.x86_64.rpm | 46 kB 00:00
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 から鍵を取得中です。
Importing GPG key 0x0608B895:
Userid : "EPEL (6) "
Fingerprint: 8c3b e96a f230 9184 da5c 0dae 3b49 df2a 0608 b895
Package : epel-release-6-8.9.amzn1.noarch (installed)
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
上記の処理を行います。よろしいでしょうか？ [y/N]y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
インストール中 : inotify-tools-3.14-2.el6.x86_64 1/1
検証中 : inotify-tools-3.14-2.el6.x86_64 1/1
インストール:
inotify-tools.x86_64 0:3.14-2.el6
完了しました!
$ inotifywait -e modify .| awk '/MODIFY/ {print $3}'
Setting up watches.
Watches established.
