⚝
One Hat Cyber Team
⚝
Your IP:
216.73.217.4
Server IP:
41.128.143.86
Server:
Linux host.raqmix.cloud 6.8.0-1025-azure #30~22.04.1-Ubuntu SMP Wed Mar 12 15:28:20 UTC 2025 x86_64
Server Software:
Apache
PHP Version:
8.3.23
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
lib
/
python3
/
dist-packages
/
cloudinit
/
__pycache__
/
View File Name :
socket.cpython-310.pyc
o 'Dg @ sr d Z ddlZddlZddlZddlZddlmZ ddlmZ ddl m Z e e Z defddZG d d d ZdS ) z#A module for common socket helpers. N)suppress) performance)DEFAULT_RUN_DIRmessagec C s t jdd}|s dS |d dkr|ddd n |d dkr#td ttjtjtjB }t d t | | | | | d W d dS 1 sOw Y dS ) z[Send a sd_notify message. :param message: sd-notify message (must be valid ascii) NOTIFY_SOCKET Nr @ /zUnsupported socket typezSending sd_notify(%s)ascii)osenvirongetreplaceOSErrorsocketAF_UNIX SOCK_DGRAM SOCK_CLOEXECLOGinfostrconnectsendallencode)r socket_pathsock r 2/usr/lib/python3/dist-packages/cloudinit/socket.py sd_notify s "r c @ s< e Zd ZdZdefddZdefddZdd Zd d Zd S ) SocketSyncz<A two way synchronization protocol over Unix domain sockets.namesc G s d| _ d| _d| _d| _d| _dd |D | _tjt dddd | j D ]*\}}t d | d }t t t | W d n1 sGw Y | | q'd S ) an Initialize a synchronization context. 1) Ensure that the socket directory exists. 2) Bind a socket for each stage. Binding the sockets on initialization allows receipt of stage "start" notifications prior to the cloud-init stage being ready to start. :param names: stage names, used as a unique identifiers r r Fc S s$ i | ]}|t t jt jt jB qS r )r r r r ).0namer r r <dictcomp>> s z'SocketSync.__init__.<locals>.<dictcomp>z/sharei T)modeexist_ok/share/z.sockN)stageremotefirst_exceptionsystemd_exit_codeexperienced_any_errorsocketsr makedirsr itemsr FileNotFoundErrorremovebind)selfr" r$ r r r r r __init__- s zSocketSync.__init__r) c C s" || j vr td| || _| S )a Set the stage before entering context. This enables the context manager to be initialized separately from each stage synchronization. :param stage: the name of a stage to synchronize Example: sync = SocketSync("stage 1", "stage 2"): with sync("stage 1"): pass with sync("stage 2"): pass zInvalid stage name: )r. ValueErrorr) )r4 r) r r r __call__M s zSocketSync.__call__c C s t tj rtd dS d| _td| j d | j | j }t d| j | d\}| _W d n1 s=w Y d|krW| ddd td t| d t d | j d t| jkrt| ddd td | j td| j d | S )zWait until a message has been received on this stage's socket. Once the message has been received, enter the context. z:Stdin is a tty, so skipping stage synchronization protocolNr zDSTATUS=Waiting on external services to complete before starting the z stage.zWaiting to start stage s startzReceived invalid message: []r( z -return.sockz Unexpected path to unix socket: zSTATUS=Running (z stage))r isattysysstdinfilenor r r, r r) r. r Timedrecvfromr* __exit__r6 r r )r4 r chunkr r r __enter__a s2 zSocketSync.__enter__c C s d| j }|r,d| _d| _t| d|j }d}| js || _t| td| | jp3t | j| _| j | j }| | j | d| d| j d | dS ) z.Notify the socket that this stage is complete.z,Completed socket interaction for boot stage r Tz in zkfatal error, run "systemctl status cloud-init-main.service" and "cloud-init status --long" for more detailszSTATUS=zecho 'z'; exit ;)r) r, r- reprtb_framer+ r fatalr boolr. r r* r r close)r4 exc_typeexc_valexc_tbr statusr r r r r@ s* zSocketSync.__exit__N) __name__ __module__ __qualname____doc__r r5 r7 rB r@ r r r r r! * s 'r! )rP loggingr r r; contextlibr cloudinitr cloudinit.settingsr getLoggerrM r r r r! r r r r <module> s