遺伝学・遺伝統計学関連の姉妹ブログ『ryamadaの遺伝学・遺伝統計学メモ』
京都大学大学院医学研究科ゲノム医学センター統計遺伝学分野のWiki
講義・スライド
医学生物学と数学とプログラミングの三重学習を狙う学習ツール
駆け足で読む○○シリーズ
ぱらぱらめくるシリーズ
カシオの計算機
オンライン整数列大辞典

１ LMPのインストール

PCクラスタ R
  • LMPのインストール
  • 動作確認
    • 一般ユーザでユーザホームディレクトリにて、koiti_yano氏のこの記事に沿ってインストールを実行。.rhostsファイル(空ファイルとしてlamのインストール前から存在する状態)やlamhostsファイル(存在しない状態)は一切いじっていない
    • まず、起動させてもいない状態で、lamhaltコマンド(lamの停止)を打ってみる。lamが動いていないよ、と警告された。
$ lamhalt

LAM 7.1.1/MPI 2 C++/ROMIO - Indiana University

-----------------------------------------------------------------------------
It seems that there is no lamd running on the host SERVER-HOGE.

This indicates that the LAM/MPI runtime environment is not operating.
The LAM/MPI runtime environment is necessary for the "lamhalt" command.

Please run the "lamboot" command the start the LAM/MPI runtime
environment.  See the LAM/MPI documentation for how to invoke
"lamboot" across multiple machines.
-----------------------------------------------------------------------------
$
    • 次にrootになってlambootコマンド(lamの開始)を打ってみる。危ないよ、と警告されて起動されない
# lamboot -v
-----------------------------------------------------------------------------
It is a Very Bad Idea to run this program as root.

LAM was designed to be run by individual users; it was *not* designed
to be run as a root-level service where multiple users use the same
LAM daemons in a client-server fashion.

Especially with today's propensity for hackers to scan for root-owned
network daemons, it could be tragic to run this program as root.
While LAM is known to be quite stable, and LAM does not leave network
sockets open for random connections after the initial setup, several
factors should strike fear into system administrator's hearts if LAM
were to be constantly running for all users to utilize:

        1. LAM leaves a Unix domain socket open on each machine in the
           /tmp directory.  So if someone breaks into root on one
           machine, they effectively have root on all machines that
           are connected via LAM.

        2. Indeed, there must have been a .rhosts (or some other trust
           mechanism) for root which must have allowed you to run LAM
           on remote nodes.  Depending on your local setup, this may
           not be safe.

        3. LAM has never been checked for buffer overflows and other
           malicious input types of errors.  We don't *think* that
           there are any buffer-overflow types of situations in LAM,
           we've never checked explicitly (hence, per Mr. Murphy,
           there are certainly some hiding somewhere).

        4. LAM programs are not audited or tracked in any way.  This
           could present a sneaky way to execute binaries without log
           trails (especially as root).

Hence, it's a Very Bad Idea to run LAM as root.  Please login as a
different user and run LAM again.
-----------------------------------------------------------------------------
#
    • 一般ユーザでlamboot -vコマンドを打つ。起動。

"-v"オプションは、verbose(冗長)オプション

$ lamboot -v

LAM 7.1.1/MPI 2 C++/ROMIO - Indiana University

n-1<30110> ssi:boot:base:linear: booting n0 (localhost)
n-1<30110> ssi:boot:base:linear: finished
$
    • 止めてみる。通常終了
$ lamhalt

LAM 7.1.1/MPI 2 C++/ROMIO - Indiana University

$