In xflock() if the file cannot be opened for reading an error (-1) is returned however if the file CAN be opened for reading (or read/write) but the 'lock' fails then a 0 is returned which is not treated as an error by the nfs-utils code. Either I am missing something or this is a bug. Could someone more knowledgeable enlighten me on this? Richard Reid Overland Storage -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
