AnonSec Shell
Server IP : 52.91.253.208  /  Your IP : 3.149.27.234   [ Reverse IP ]
Web Server : Apache
System : Linux ip-172-26-9-9 4.19.0-25-cloud-amd64 #1 SMP Debian 4.19.289-1 (2023-07-24) x86_64
User : daemon ( 1)
PHP Version : 7.3.18
Disable Function : NONE
Domains : 3 Domains
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : OFF
Directory :  /lib/systemd/system/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ HOME ]     [ BACKUP SHELL ]     [ JUMPING ]     [ MASS DEFACE ]     [ SCAN ROOT ]     [ SYMLINK ]     

Current File : /lib/systemd/system/cloud-config.target
# cloud-init normally emits a "cloud-config" upstart event to inform third
# parties that cloud-config is available, which does us no good when we're
# using systemd.  cloud-config.target serves as this synchronization point
# instead.  Services that would "start on cloud-config" with upstart can
# instead use "After=cloud-config.target" and "Wants=cloud-config.target"
# as appropriate.

[Unit]
Description=Cloud-config availability
Wants=cloud-init-local.service cloud-init.service
After=cloud-init-local.service cloud-init.service

Anon7 - 2022
AnonSec Team