Linux localhost.localdomain 3.10.0-1160.80.1.el7.x86_64 #1 SMP Tue Nov 8 15:48:59 UTC 2022 x86_64
Apache
: 10.29.51.72 | : 216.73.216.153
Cant Read [ /etc/named.conf ]
7.2.34
apache
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
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
cluster /
[ HOME SHELL ]
Name
Size
Permission
Action
relaxng
[ DIR ]
drwxr-xr-x
ASEHAagent.sh.metadata
3.89
KB
-rw-r--r--
SAPDatabase.metadata
5.52
KB
-rw-r--r--
SAPInstance.metadata
3.91
KB
-rw-r--r--
apache.sh.metadata
3.03
KB
-rw-r--r--
bind-mount.sh.metadata
1.72
KB
-rw-r--r--
clusterfs.sh.metadata
5.48
KB
-rw-r--r--
db2.sh.metadata
1.58
KB
-rw-r--r--
drbd.sh.metadata
1.39
KB
-rw-r--r--
fence_mpath_check
9.98
KB
-rwxr-xr-x
fence_mpath_check_hardreboot
9.98
KB
-rwxr-xr-x
fence_scsi_check
15.95
KB
-rwxr-xr-x
fence_scsi_check.pl
15.95
KB
-rwxr-xr-x
fence_scsi_check_hardreboot
15.95
KB
-rwxr-xr-x
fs.sh.metadata
6.65
KB
-rw-r--r--
ip.sh.metadata
4.13
KB
-rw-r--r--
lvm.sh.metadata
2.31
KB
-rw-r--r--
mysql.sh.metadata
3.01
KB
-rw-r--r--
named.sh.metadata
3.2
KB
-rw-r--r--
netfs.sh.metadata
4.74
KB
-rw-r--r--
nfsclient.sh.metadata
4.74
KB
-rw-r--r--
nfsexport.sh.metadata
2.42
KB
-rw-r--r--
nfsserver.sh.metadata
3.16
KB
-rw-r--r--
openldap.sh.metadata
2.86
KB
-rw-r--r--
oracledb.sh.metadata
3.69
KB
-rw-r--r--
orainstance.sh.metadata
2.84
KB
-rw-r--r--
oralistener.sh.metadata
2.05
KB
-rw-r--r--
postgres-8.sh.metadata
3.17
KB
-rw-r--r--
samba.sh.metadata
2.49
KB
-rw-r--r--
script.sh.metadata
1.77
KB
-rw-r--r--
service.sh.metadata
7.58
KB
-rw-r--r--
smb.sh.metadata
1.78
KB
-rw-r--r--
tomcat-6.sh.metadata
2.15
KB
-rw-r--r--
vm.sh.metadata
9.66
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : fs.sh.metadata
<?xml version="1.0" encoding="ISO-8859-1" ?> <!DOCTYPE resource-agent SYSTEM "ra-api-1-modified.dtd"> <resource-agent name="fs" version="rgmanager 2.0"> <version>1.0</version> <longdesc lang="en"> This defines a standard file system mount (= not a clustered or otherwise shared file system). </longdesc> <shortdesc lang="en"> Defines a file system mount. </shortdesc> <parameters> <parameter name="name" primary="1"> <longdesc lang="en"> Symbolic name for this file system. </longdesc> <shortdesc lang="en"> File System Name </shortdesc> <content type="string"/> </parameter> <parameter name="mountpoint" unique="1" required="1"> <longdesc lang="en"> Path in file system heirarchy to mount this file system. </longdesc> <shortdesc lang="en"> Mount Point </shortdesc> <content type="string"/> </parameter> <parameter name="device" unique="1" required="1"> <longdesc lang="en"> Block device, file system label, or UUID of file system. </longdesc> <shortdesc lang="en"> Device or Label </shortdesc> <content type="string"/> </parameter> <parameter name="fstype"> <longdesc lang="en"> File system type. If not specified, mount(8) will attempt to determine the file system type. </longdesc> <shortdesc lang="en"> File system type </shortdesc> <content type="string"/> </parameter> <parameter name="force_unmount"> <longdesc lang="en"> If set, the cluster will kill all processes using this file system when the resource group is stopped. Otherwise, the unmount will fail, and the resource group will be restarted. </longdesc> <shortdesc lang="en"> Force Unmount </shortdesc> <content type="boolean"/> </parameter> <parameter name="quick_status"> <longdesc lang="en"> Use quick status checks. When set to 0 (the default), this agent behaves normally. When set to 1, this agent will not log errors incurred or perform the file system accessibility check (e.g. it will not try to read from/write to the file system). You should only set this to 1 if you have lots of file systems on your cluster or you are seeing very high load spikes as a direct result of this agent. </longdesc> <shortdesc lang="en"> Quick/brief status checks. </shortdesc> <content type="boolean"/> </parameter> <parameter name="self_fence"> <longdesc lang="en"> If set and unmounting the file system fails, the node will immediately reboot. Generally, this is used in conjunction with force_unmount support, but it is not required. </longdesc> <shortdesc lang="en"> Seppuku Unmount </shortdesc> <content type="boolean"/> </parameter> <parameter name="nfslock" inherit="nfslock"> <longdesc lang="en"> If set and unmounting the file system fails, the node will try to kill lockd and issue reclaims across all remaining network interface cards. </longdesc> <shortdesc lang="en"> Enable NFS lock workarounds </shortdesc> <content type="boolean"/> </parameter> <parameter name="nfsrestart"> <longdesc lang="en"> If set and unmounting the file system fails, the node will try to restart nfs daemon and nfs lockd to drop all filesystem references. Use this option as last resource. This option requires force_unmount to be set and it is not compatible with nfsserver resource. </longdesc> <shortdesc lang="en"> Enable NFS daemon and lockd workaround </shortdesc> <content type="boolean"/> </parameter> <parameter name="fsid"> <longdesc lang="en"> File system ID for NFS exports. This can be overridden in individual nfsclient entries. </longdesc> <shortdesc lang="en"> NFS File system ID </shortdesc> <content type="string"/> </parameter> <parameter name="force_fsck"> <longdesc lang="en"> If set, the file system will be checked (even if it is a journalled file system). This option is ignored for non-journalled file systems such as ext2. </longdesc> <shortdesc lang="en"> Force fsck support </shortdesc> <content type="boolean"/> </parameter> <parameter name="options"> <longdesc lang="en"> Options used when the file system is mounted. These are often file-system specific. See mount(8) for supported mount options. </longdesc> <shortdesc lang="en"> Mount Options </shortdesc> <content type="string"/> </parameter> <parameter name="use_findmnt"> <longdesc lang="en"> Use findmnt to determine if and where a filesystem is mounted. Disabling this uses the failback method (should be used if autofs maps are located on network storage (ie. nfs, iscsi, etc). </longdesc> <shortdesc lang="en"> Utilize findmnt to detect if and where filesystems are mounted </shortdesc> <content type="boolean"/> </parameter> </parameters> <actions> <action name="start" timeout="900"/> <action name="stop" timeout="30"/> <!-- Recovery isn't possible; we don't know if resources are using the file system. --> <!-- Checks to see if it's mounted in the right place --> <action name="status" interval="1m" timeout="10"/> <action name="monitor" interval="1m" timeout="10"/> <!-- Note: active monitoring is constant and supplants all check depths --> <!-- Checks to see if we can read from the mountpoint --> <action name="status" depth="10" timeout="30" interval="30"/> <action name="monitor" depth="10" timeout="30" interval="30"/> <!-- Checks to see if we can write to the mountpoint (if !ROFS) --> <action name="status" depth="20" timeout="30" interval="1m"/> <action name="monitor" depth="20" timeout="30" interval="1m"/> <action name="meta-data" timeout="5"/> <action name="validate-all" timeout="5"/> </actions> <special tag="rgmanager"> <attributes maxinstances="1"/> <child type="fs" start="1" stop="3"/> <child type="clusterfs" start="1" stop="3"/> <child type="nfsexport" start="3" stop="1"/> </special> </resource-agent>
Close