Linux ip-148-66-134-25.ip.secureserver.net 3.10.0-1160.119.1.el7.tuxcare.els10.x86_64 #1 SMP Fri Oct 11 21:40:41 UTC 2024 x86_64
Apache
: 148.66.134.25 | : 18.188.140.232
66 Domain
8.0.30
amvm
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
nfs-utils-1.3.0 /
[ HOME SHELL ]
Name
Size
Permission
Action
ChangeLog
2.34
KB
-rw-r--r--
KNOWNBUGS
1.03
KB
-rw-r--r--
NEW
10.09
KB
-rw-r--r--
README
2.25
KB
-rw-r--r--
THANKS
291
B
-rw-r--r--
TODO
4.41
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : KNOWNBUGS
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.
Close