| Server IP : 101.53.144.229 / Your IP : 216.73.216.104 Web Server : Apache System : Linux host.gdigitalindia.in 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 User : digitalshiksha ( 1179) PHP Version : 5.6.40 Disable Function : eval,show_source,system,shell_exec,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,dl,show_source,curl_multi_exechellcmd, ini_restore,apache_get_modules,get_cfg_var,passthru, exec ,proc_get_status,fpassthru,c999_buff_prepare,c999_sess_put,c99_buff_prepare,c99_sess_put,proc_close,ini_alter,dl,symlink,link,proc_close,ini_alter,dl,symlink,link,mail MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/nfs-utils-1.3.0/ |
Upload File : |
nfsd: * We currently keep the inode in the exports struct. This is a bad idea with directories that are intended to be used as a mount point. Must store the file name instead and do a lookup when getfh is called. Yuck! Even yuckier: what do we do about exports matching when we can't keep the inode number? * stating a file on remote cdrom returns st_blocks == 0 for some apps. * Should allow multiple exports per dev if one of the directories isn't a subdir of the other. nfsclnt: * On some occasions, an EAGAIN reported by the transport layer will be propagated to the VFS. * Some operations do not seem to release the inode properly, so unmounting the device fails. lockd: * Handle portmap registration in a separate thread. portmap may not be running when we try to mount the first NFS volume (esp. when mounting /usr). * Does not inform rpc.statd when hosts no longer require monitoring; hosts are incorrectly monitored until next system reboot. exportfs/mountd: * Export handling is reported to do odd things at times.