| Change times in amq RPCs to be longlong_t instead of long, to avoid 2038 issue on 32 bit machines. This makes the amq RPC incompatible with older versions of amd. It is too much work to provide backwards compatibility for little benefit, but it can be done. Fix core-dump in amq -i. |
|
More...
|
about 4 years ago
|
| Update the ctime of the directory too, since it changed. From Mark Davies |
|
More...
|
over 10 years ago
|
| * Make hasmntval() return an 0 on error, 1 on success and place the value in an argument. Update all users and check properly for errors. Get rid of hasmntvalerr(). * Add hasmntvaldelim() which takes a string delimiter. This is now used to chop vers=4.1 to 4, so that we can parse the version correctly (we don't care about the .1 part yet) |
|
More...
|
over 10 years ago
|
| Today's change |
|
More...
|
over 10 years ago
|
| Fix SEGV on amq entries that print times. |
|
More...
|
over 10 years ago
|
| Today's RPC ping change. |
|
More...
|
over 10 years ago
|
| - There is really no ti-rpc nfsv4, so don't send one; instead send a v3 for now. |
|
More...
|
over 10 years ago
|
| Today's changes |
|
More...
|
over 10 years ago
|
| - add more debugging in the unmount path - if the EXPIRE_MULTI call fails, with EAGAIN, fail back to the EXPIRE call seems to fix unmounting with nfsv4 volumes. |
|
More...
|
over 10 years ago
|
| Improve debugging for unmounting. |
|
More...
|
over 10 years ago
|
| Mention today's changes. |
|
More...
|
over 10 years ago
|
| Default to "string" mount options for NFSv4 because the kernel does not properly handle the auth_flavours[] field. Tested with nfs-utils-1.3.3 and it always defaults to krb5i if string options are not used. Please note that the "rw" option is not recognized by the linux kernel. |
|
More...
|
over 10 years ago
|
| 1. Add the "sys" alias for "unix", as well as "none", and "null" 2. Properly handle multiple flavors, although the linux kernel does not (yet?) 3. Don't add the "sec=" field, because it is already there. |
|
More...
|
over 10 years ago
|
| Today's change summary. |
|
More...
|
over 10 years ago
|
| The definition of the wcc post op attributes should be am_fattr3 not am_wcc_attr in unlink3_or_rmdir3(). |
|
More...
|
over 10 years ago
|
| The nfs_quick_reply() functionality relies on taking a copy of the current transport for later use. |
|
More...
|
over 10 years ago
|
| The NFS v2 internal server uses several validation checks for each RPC request it receives, also add this validation for the NFS v3 internal server. |
|
More...
|
over 10 years ago
|
| The implementation of the NFS v3 server does not use the hack needed by the nfs_quick_reply() function. |
|
More...
|
over 10 years ago
|
| The nfs_quick_reply() function needs to know the current RPC transport outside of the NFS LOOKUP method call. It needs this to reply to the NFS LOOKUP call that initiated the mount. |
|
More...
|
over 10 years ago
|
| The nfs_quick_reply() functionality relies on taking a copy of the current transport for later use. |
|
More...
|
over 10 years ago
|
| Recent Linux NFS uses a simulated attibute cache change detection method based on ctime. Consequenty the amd use of mtime for this doesn't work properly for some kernel versions. |
|
More...
|
over 10 years ago
|
| today's fixes |
|
More...
|
over 10 years ago
|
| The function unlink3_or_rmdir3() is called by both NFSv3 remove and rmdir methods. Both these methods require post op wcc attributes to be returned but unlink3_or_rmdir3() was returning only the pre op wcc attributes. (Ian Kent) |
|
More...
|
over 10 years ago
|
| The NFSv3 readdir method is expected to return the attributes of the directory being read for both the success and failure cases. (Ian Kent) |
|
More...
|
over 10 years ago
|
| The NFSv3 lookup method, which returns attributes for the directory containing the object to be looked up, used incorrect mount point attributes. This was causing unusual file system object visibility problems. (Ian Kent) |
|
More...
|
over 10 years ago
|
| When the NFSv3 access method is called and there is no correspoding mount point for the path we requested, we need to return ESTALE so that the kernel will then perform an NFSv3 lookup and the mount point will be re-mounted. |
|
More...
|
over 10 years ago
|
| Add log trace print to NFSv3 readdirplus for debugging purposes (Ian Kent) |
|
More...
|
over 10 years ago
|
| Fix nfs args setting code (raven at the maw dot net) |
|
More...
|
over 11 years ago
|
| don't use logical && when & is meant |
|
More...
|
over 11 years ago
|
| make sure variables are initialized |
|
More...
|
over 11 years ago
|
