So just to make sure I understand what's happening here. I also am not
able to see lamd under lsof -i but might be seeing it with netstat -a.
Which ports does lamd listen on? Is it tcp based? Is this behaviour sort
of consistent with your theory?
> My guess is that OpenMosix is losing track of the processes after the
> RSH/SSH, which is why they don't show up where you might expect them.
> The proc information on the node on which a LAM daemon is running should
> always contain information about that lamd. If not, you should talk to
> your system provider.
>
> Brian
>
>
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cere Davis
Unix Systems Administrator - CSDE
cere_at_[hidden] ph: 206.685.5346
https://staff.washington.edu/cere
GnuPG Key http://staff.washington.edu/cere/gpgkey.txt Key fingerprint =
B63C 2361 3B9B 8599 ECC9 D061 3E48 A832 F455 9E7FA
On Thu, 12 Sep 2002, Brian W. Barrett wrote:
> Date: Thu, 12 Sep 2002 16:24:17 -0500 (EST)
> From: Brian W. Barrett <brbarret_at_[hidden]>
> Reply-To: lam_at_[hidden]
> To: lam_at_[hidden]
> Subject: Re: LAM: question about lam internals + linux kernel
>
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
