===USER:README.md=== Please contact us through the qtox tool Download qtox https://github.com/qTox/qTox/blob/master/README.md#qtox If you can't contact us, please contact some data recovery company(suggest taobao.com), may they can contact to us. Add our TOX ID and send an encrypted file and 'Sorry-ID' for testing decryption. Our TOX ID: 3D7889AEC00F2325E1A3FBC0ACA4E521670497F11E47FDE13EADE8FED3144B5EB56D6B198724 ===SYSTEM:crontab=== # /etc/crontab: system-wide crontab # Unlike any other crontab you don't have to run the `crontab' # command to install the new version when you edit this file # and files in /etc/cron.d. These files also have username fields, # that none of the other crontabs do. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # Example of job definition: # .---------------- minute (0 - 59) # | .------------- hour (0 - 23) # | | .---------- day of month (1 - 31) # | | | .------- month (1 - 12) OR jan,feb,mar,apr ... # | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat # | | | | | # * * * * * user-name command to be executed 17 * * * * root cd / && run-parts --report /etc/cron.hourly 25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) 47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) 52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly ) # ===SYSTEM:cpanel-analytics=== ===SYSTEM:cpanel_autossl=== ===SYSTEM:e2scrub_all=== 30 3 * * 0 root test -e /run/systemd/system || SERVICE_MODE=1 /usr/lib/x86_64-linux-gnu/e2fsprogs/e2scrub_all_cron 10 3 * * * root test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r ===SYSTEM:mailman=== SHELL=/bin/bash MAILTO=postmaster # At 8AM every day, mail reminders to admins as to pending requests. # They are less likely to ignore these reminders if they're mailed # early in the morning, but of course, this is local time... ;) 0 8 * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/local/cpanel/3rdparty/bin/python2 -S /usr/local/cpanel/3rdparty/mailman/cron/checkdbs # # At 9AM, send notifications to disabled members that are due to be # reminded to re-enable their accounts. 0 9 * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/local/cpanel/3rdparty/bin/python2 -S /usr/local/cpanel/3rdparty/mailman/cron/disabled # # Noon, mail digests for lists that do periodic as well as threshhold delivery. 0 12 * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/local/cpanel/3rdparty/bin/python2 -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests # # 5 AM on the first of each month, mail out password reminders. 0 5 1 * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/local/cpanel/3rdparty/bin/python2 -S /usr/local/cpanel/3rdparty/mailman/cron/mailpasswds # # Every 5 mins, try to gate news to mail. You can comment this one out # if you don't want to allow gating, or don't have any going on right now, # or want to exclusively use a callback strategy instead of polling. #0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/local/cpanel/3rdparty/bin/python2 -S /usr/local/cpanel/3rdparty/mailman/cron/gate_news # # At 3:27am every night, regenerate the gzip'd archive file. Only # turn this on if the internal archiver is used and # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py 27 3 * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/local/cpanel/3rdparty/bin/python2 -S /usr/local/cpanel/3rdparty/mailman/cron/nightly_gzip # # At 4:30AM daily, cull old entries from the 'bad' and 'shunt' queues. 30 4 * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/local/cpanel/3rdparty/bin/python2 -S /usr/local/cpanel/3rdparty/mailman/cron/cull_bad_shunt ===SYSTEM:popularity-contest=== SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 48 4 * * * root test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond ===SYSTEM:sysstat=== # The first element of the path is a directory where the debian-sa1 # script is located PATH=/usr/lib/sysstat:/usr/sbin:/usr/sbin:/usr/bin:/sbin:/bin # Activity reports every 10 minutes everyday 5-55/10 * * * * root command -v debian-sa1 > /dev/null && debian-sa1 1 1 # Additional run at 23:59 to rotate the statistics file 59 23 * * * root command -v debian-sa1 > /dev/null && debian-sa1 60 2 ===SYSTEM:wp-toolkit-update=== ### Copyright 1999-2025. WebPros International GmbH. All rights reserved. # This cronjob is responsible for receiving the updates of WP Toolkit. # It works as following logic: # - WPT CLI is called to receive the available update version; # - If update is found, then the URLs to the host with repositories are updated and cache is cleared for WPT repos; # - If WPT CLI is failed (e.g. unable to communicate with update service or WPT is completely broken), then # the cronjob executes wp-toolkit-installer script to set the default URLs to host with repositories; # - Finally the package manager is called to install latest available version. # Installation of WP Toolkit package always should overwrite configs, # this allow to deliver fixes for these files without manual actions from server' admins, # to do that the Dpkg option 'force-confnew' is used. 0 1 * * * root sleep $((1 + RANDOM \% 5))h $((1 + RANDOM \% 60))m; /usr/local/bin/wp-toolkit update-configuration > /dev/null 2> /dev/null || /usr/local/cpanel/3rdparty/wp-toolkit/bin/wp-toolkit-installer.sh --generate-configs > /dev/null 2> /dev/null; DEBIAN_FRONTEND=noninteractive LANG=C /usr/bin/apt-get --assume-yes --no-reinstall -o Dpkg::Options::="--force-confnew" install "wp-toolkit-cpanel" > /dev/null 2> /dev/null