Christoph Lameter wrote:
> On Tue, 30 Jan 2007, Martin MOKREJS wrote:
>
>> Hi,
>> is this a known issue? Should I bother to upgrade to 2.6.19.2 if it
>> contains the fix?
>> Thank you any help. It might be related to NFS. The machine in question is
>> NFSv3 client,
>> udp. And used for
Christoph Lameter wrote:
On Tue, 30 Jan 2007, Martin MOKREJS wrote:
Hi,
is this a known issue? Should I bother to upgrade to 2.6.19.2 if it
contains the fix?
Thank you any help. It might be related to NFS. The machine in question is
NFSv3 client,
udp. And used for computations. The
On Tue, 30 Jan 2007, Martin MOKREJ wrote:
> Hi,
> is this a known issue? Should I bother to upgrade to 2.6.19.2 if it
> contains the fix?
> Thank you any help. It might be related to NFS. The machine in question is
> NFSv3 client,
> udp. And used for computations. The process which died is
On Tue, 30 Jan 2007, Martin MOKREJ wrote:
Hi,
is this a known issue? Should I bother to upgrade to 2.6.19.2 if it
contains the fix?
Thank you any help. It might be related to NFS. The machine in question is
NFSv3 client,
udp. And used for computations. The process which died is from
Hi,
is this a known issue? Should I bother to upgrade to 2.6.19.2 if it contains
the fix?
Thank you any help. It might be related to NFS. The machine in question is
NFSv3 client,
udp. And used for computations. The process which died is from torque cluster
management
package.
Please Cc: me
Hi,
is this a known issue? Should I bother to upgrade to 2.6.19.2 if it contains
the fix?
Thank you any help. It might be related to NFS. The machine in question is
NFSv3 client,
udp. And used for computations. The process which died is from torque cluster
management
package.
Please Cc: me
6 matches
Mail list logo