Thank you .
But I tried lamboot -v < /dev/null or any file as
input, it still didn't work.
Any idea?
Thanks.
Shi Jin
--- "Brian W. Barrett" <brbarret_at_[hidden]> wrote:
> On Mar 15, 2004, at 6:59 PM, Shi Jin wrote:
>
> > I have this minor issue for about two years.
> Whenever
> > I run lamboot on the shell, I cannot exit that
> shell,
> > no matter how many nodes are involved. And there
> is no
> > such a problem if I am sitting on the computer
> > localling. any thing involes ssh will die.
> > Just a simple test,
> > do lamboot -v on the machine you are currently
> sitting
> > at, you can exit.
> > if you first ssh localhost, and then lamboot -v ,
> you
> > won't be able to exit.
>
> You have stumbled upon some Unix lore here. The
> problem is the stdin
> file descriptor, as ssh will not return if stdin is
> still open. A
> simple solution is to run lamboot with something
> like "lamboot -v <
> /dev/null" so that stdin is closed from the start.
> In the future, we
> might close stdin internally, but there are some
> legacy reasons that
> the code is the way it is.
>
> Hope this helps,
>
> Brian
>
> --
> Brian Barrett
> LAM/MPI developer and all around nice guy
> Have a LAM/MPI day: http://www.lam-mpi.org/
>
> _______________________________________________
> This list is archived at
http://www.lam-mpi.org/MailArchives/lam/
__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com
|
