Cannot assign prosessor number

[thomasn]

What is wrong ? :
07:00:26 NFSNET Client - $Revision: 1.17 $
07:00:26 Cannot assign processor number, sleeping for 10 seconds.
Last message was:
07:00:36 Cannot assign processor number, sleeping for 20 seconds.
Last message was:
07:00:56 Cannot assign processor number, sleeping for 40 seconds.
Last message was:
07:01:36 Cannot assign processor number, sleeping for 80 seconds.
Last message was:
07:02:56 Cannot assign processor number, sleeping for 160 seconds.
Last message was:
07:05:36 Cannot assign processor number, sleeping for 320 seconds.
Last message was:
07:10:56 Cannot assign processor number, sleeping for 640 seconds.
Last message was:

I tried an hour ago to register and start running the client.
After running nfsnetinit, I ran nfsnetclient, and got the above error message.

Running the linux static binary on an P4 2.4 Ghz machine.

Thomas

[xilman]

Originally Posted by thomasn

What is wrong ? :
07:00:26 NFSNET Client - $Revision: 1.17 $
07:00:26 Cannot assign processor number, sleeping for 10 seconds.
Last message was:

...

I tried an hour ago to register and start running the client.
After running nfsnetinit, I ran nfsnetclient, and got the above error message.

Running the linux static binary on an P4 2.4 Ghz machine.

Thomas

This message appears when a lock file can't be obtained. It usually means that more than one nfsnetclient processs is running on a single cpu system. Please check that isn't the case with your machine.

It can sometimes happen if the permissions on the processors or processors/p0 directory are very weird, for instance if a file can be created but not deleted. This is certainly possible with the Unix filesystem semantics but it is usually quite tricky to arrange (it's much easier with NTFS).


Paul