In lockf(3), the description of EDEADLK says that it can occur with the T_LOCK operation. That should be F_LOCK. The presence of the T makes it look like maybe F_TLOCK was intended, but that would be wrong. Only the blocking F_LOCK operation can cause EDEADLK. Also, I was looking through Changes.old for the last few versions, and noticed that fcntl.h was misspelled fntl.h a couple of times. -- Alan Curry -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html