Hacked By AnonymousFox
3
u1�W�Q � @ s� d Z ddlmZmZmZmZ ddlZddlZddlm Z ddl
m Z ddl m
Z
ddlmZ ddlmZ dd lmZ dd
lmZ G d d � d e�ZG d
d� de �ZdS )z�
pyudev.monitor
==============
Monitor implementation.
.. moduleauthor:: Sebastian Wiesner <lunaryorn@gmail.com>
� )�print_function�division�unicode_literals�absolute_importN)�Thread)�partial)�Device)�eintr_retry_call)�ensure_byte_string)�pipe)�pollc @ s� e Zd ZdZdd� Zdd� Zed"dd��Zed d
� �Z d d � Z
d#dd�Z dd� Z dd� Z
dd� Zdd� Zdd� Zdd� Zd$d d �Zd d � Zd d!� Zd
S )%�Monitorat
A synchronous device event monitor.
A :class:`Monitor` objects connects to the udev daemon and listens for
changes to the device list. A monitor is created by connecting to the
kernel daemon through netlink (see :meth:`from_netlink`):
>>> from pyudev import Context, Monitor
>>> context = Context()
>>> monitor = Monitor.from_netlink(context)
Once the monitor is created, you can add a filter using :meth:`filter_by()`
or :meth:`filter_by_tag()` to drop incoming events in subsystems, which are
not of interest to the application:
>>> monitor.filter_by('input')
When the monitor is eventually set up, you can either poll for events
synchronously:
>>> device = monitor.poll(timeout=3)
>>> if device:
... print('{0.action}: {0}'.format(device))
...
Or you can monitor events asynchronously with :class:`MonitorObserver`.
To integrate into various event processing frameworks, the monitor provides
a :func:`selectable <select.select>` file description by :meth:`fileno()`.
However, do *not* read or write directly on this file descriptor.
Instances of this class can directly be given as ``udev_monitor *`` to
functions wrapped through :mod:`ctypes`.
.. versionchanged:: 0.16
Remove :meth:`from_socket()` which is deprecated, and even removed in
recent udev versions.
c C s || _ || _|j| _d| _d S )NF)�contextZ_as_parameter_�_libudev�_started)�selfr Z monitor_p� r � /usr/lib/python3.6/monitor.py�__init__V s zMonitor.__init__c C s | j j| � d S )N)r Zudev_monitor_unref)r r r r �__del__\ s zMonitor.__del__�udevc C s> |dkrt dj|���|jj|t|��}|s4td��| ||�S )a�
Create a monitor by connecting to the kernel daemon through netlink.
``context`` is the :class:`Context` to use. ``source`` is a string,
describing the event source. Two sources are available:
``'udev'`` (the default)
Events emitted after udev as registered and configured the device.
This is the absolutely recommended source for applications.
``'kernel'``
Events emitted directly after the kernel has seen the device. The
device has not yet been configured by udev and might not be usable
at all. **Never** use this, unless you know what you are doing.
Return a new :class:`Monitor` object, which is connected to the
given source. Raise :exc:`~exceptions.ValueError`, if an invalid
source has been specified. Raise
:exc:`~exceptions.EnvironmentError`, if the creation of the monitor
failed.
�kernelr z8Invalid source: {0!r}. Must be one of "udev" or "kernel"z Could not create udev monitor)r r )�
ValueError�formatr Z udev_monitor_new_from_netlinkr
�EnvironmentError)�clsr �source�monitorr r r � from_netlink_ s zMonitor.from_netlinkc C s | j S )z�
``True``, if this monitor was started, ``False`` otherwise. Readonly.
.. seealso:: :meth:`start()`
.. versionadded:: 0.16
)r )r r r r �started s zMonitor.startedc C s | j j| �S )z�
Return the file description associated with this monitor as integer.
This is really a real file descriptor ;), which can be watched and
:func:`select.select`\ ed.
)r Zudev_monitor_get_fd)r r r r �fileno� s zMonitor.filenoNc C s8 t |�}|dk rt |�}| jj| ||� | jj| � dS )a
Filter incoming events.
``subsystem`` is a byte or unicode string with the name of a
subsystem (e.g. ``'input'``). Only events originating from the
given subsystem pass the filter and are handed to the caller.
If given, ``device_type`` is a byte or unicode string specifying the
device type. Only devices with the given device type are propagated
to the caller. If ``device_type`` is not given, no additional
filter for a specific device type is installed.
These filters are executed inside the kernel, and client processes
will usually not be woken up for device, that do not match these
filters.
.. versionchanged:: 0.15
This method can also be after :meth:`start()` now.
N)r
r Z/udev_monitor_filter_add_match_subsystem_devtype�udev_monitor_filter_update)r Z subsystemZ device_typer r r � filter_by� s
zMonitor.filter_byc C s" | j j| t|�� | j j| � dS )aR
Filter incoming events by the given ``tag``.
``tag`` is a byte or unicode string with the name of a tag. Only
events for devices which have this tag attached pass the filter and are
handed to the caller.
Like with :meth:`filter_by` this filter is also executed inside the
kernel, so that client processes are usually not woken up for devices
without the given ``tag``.
.. udevversion:: 154
.. versionadded:: 0.9
.. versionchanged:: 0.15
This method can also be after :meth:`start()` now.
N)r Z!udev_monitor_filter_add_match_tagr
r! )r �tagr r r �
filter_by_tag� s zMonitor.filter_by_tagc C s | j j| � | j j| � dS )a
Remove any filters installed with :meth:`filter_by()` or
:meth:`filter_by_tag()` from this monitor.
.. warning::
Up to udev 181 (and possibly even later versions) the underlying
``udev_monitor_filter_remove()`` seems to be broken. If used with
affected versions this method always raises
:exc:`~exceptions.ValueError`.
Raise :exc:`~exceptions.EnvironmentError` if removal of installed
filters failed.
.. versionadded:: 0.15
N)r Zudev_monitor_filter_remover! )r r r r �
remove_filter� s zMonitor.remove_filterc C s ddl }|jdt� | j� dS )a�
Switch the monitor into listing mode.
Connect to the event source and receive incoming events. Only after
calling this method, the monitor listens for incoming events.
.. note::
This method is implicitly called by :meth:`__iter__`. You don't
need to call it explicitly, if you are iterating over the
monitor.
.. deprecated:: 0.16
Will be removed in 1.0. Use :meth:`start()` instead.
r Nz4Will be removed in 1.0. Use Monitor.start() instead.)�warnings�warn�DeprecationWarning�start)r r& r r r �enable_receiving� s zMonitor.enable_receivingc C s* | j s&| jj| � tj| tj� d| _ dS )a�
Start this monitor.
The monitor will not receive events until this method is called. This
method does nothing if called on an already started :class:`Monitor`.
.. note::
Typically you don't need to call this method. It is implicitly
called by :meth:`poll()` and :meth:`__iter__()`.
.. seealso:: :attr:`started`
.. versionchanged:: 0.16
This method does nothing if the :class:`Monitor` was already
started.
TN)r r Z udev_monitor_enable_receivingr Zset_fd_status_flag�os�
O_NONBLOCK)r r r r r) � s z
Monitor.startc C s | j j| |� dS )aN
Set the receive buffer ``size``.
``size`` is the requested buffer size in bytes, as integer.
.. note::
The CAP_NET_ADMIN capability must be contained in the effective
capability set of the caller for this method to succeed. Otherwise
:exc:`~exceptions.EnvironmentError` will be raised, with ``errno``
set to :data:`~errno.EPERM`. Unprivileged processes typically lack
this capability. You can check the capabilities of the current
process with the python-prctl_ module:
>>> import prctl
>>> prctl.cap_effective.net_admin
Raise :exc:`~exceptions.EnvironmentError`, if the buffer size could not
bet set.
.. versionadded:: 0.13
.. _python-prctl: http://packages.python.org/python-prctl
N)r Z$udev_monitor_set_receive_buffer_size)r �sizer r r �set_receive_buffer_size s z Monitor.set_receive_buffer_sizec C sv xpy | j j| �}|r t| j|�S dS tk
rl } z.|jtjtjfkrJdS |jtjkrZwn� W Y dd}~X qX qW dS )z�Receive a single device from the monitor.
Return the received :class:`Device`, or ``None`` if no device could be
received.
N) r Zudev_monitor_receive_devicer r r �errnoZEAGAINZ EWOULDBLOCKZEINTR)r Zdevice_p�errorr r r �_receive_device s zMonitor._receive_devicec C sL |dk r |dkr t |d �}| j� ttjj| df�j|�rD| j� S dS dS )a�
Poll for a device event.
You can use this method together with :func:`iter()` to synchronously
monitor events in the current thread::
for device in iter(monitor.poll, None):
print('{0.action} on {0.device_path}'.format(device))
Since this method will never return ``None`` if no ``timeout`` is
specified, this is effectively an endless loop. With
:func:`functools.partial()` you can also create a loop that only waits
for a specified time::
for device in iter(partial(monitor.poll, 3), None):
print('{0.action} on {0.device_path}'.format(device))
This loop will only wait three seconds for a new device event. If no
device event occurred after three seconds, the loop will exit.
``timeout`` is a floating point number that specifies a time-out in
seconds. If omitted or ``None``, this method blocks until a device
event is available. If ``0``, this method just polls and will never
block.
.. note::
This method implicitly calls :meth:`start()`.
Return the received :class:`Device`, or ``None`` if a timeout
occurred. Raise :exc:`~exceptions.EnvironmentError` if event retrieval
failed.
.. seealso::
:attr:`Device.action`
The action that created this event.
:attr:`Device.sequence_number`
The sequence number of this event.
.. versionadded:: 0.16
Nr i� �r)�intr) r r �Poll�
for_eventsr1 )r �timeoutr r r r 5 s , z Monitor.pollc C s& ddl }|jdt� | j� }|j|fS )a:
Receive a single device from the monitor.
.. warning::
You *must* call :meth:`start()` before calling this method.
The caller must make sure, that there are events available in the
event queue. The call blocks, until a device is available.
If a device was available, return ``(action, device)``. ``device``
is the :class:`Device` object describing the device. ``action`` is
a string describing the action. Usual actions are:
``'add'``
A device has been added (e.g. a USB device was plugged in)
``'remove'``
A device has been removed (e.g. a USB device was unplugged)
``'change'``
Something about the device changed (e.g. a device property)
``'online'``
The device is online now
``'offline'``
The device is offline now
Raise :exc:`~exceptions.EnvironmentError`, if no device could be
read.
.. deprecated:: 0.16
Will be removed in 1.0. Use :meth:`Monitor.poll()` instead.
r Nz3Will be removed in 1.0. Use Monitor.poll() instead.)r& r' r( r �action)r r& �devicer r r �receive_devicej s
zMonitor.receive_devicec c sB ddl }|jdt� | j� x | j� }|dk r |j|fV q W dS )a�
Wait for incoming events and receive them upon arrival.
This methods implicitly calls :meth:`start()`, and starts polling the
:meth:`fileno` of this monitor. If a event comes in, it receives the
corresponding device and yields it to the caller.
The returned iterator is endless, and continues receiving devices
without ever stopping.
Yields ``(action, device)`` (see :meth:`receive_device` for a
description).
.. deprecated:: 0.16
Will be removed in 1.0. Use an explicit loop over :meth:`poll()`
instead, or monitor asynchronously with :class:`MonitorObserver`.
r NzuWill be removed in 1.0. Use an explicit loop over "poll()" instead, or monitor asynchronously with "MonitorObserver".)r& r' r( r) r r7 )r r& r8 r r r �__iter__� s zMonitor.__iter__)r )N)N)�__name__�
__module__� __qualname__�__doc__r r � classmethodr �propertyr r r" r$ r% r* r) r. r1 r r9 r: r r r r r
. s" &
5&r
c @ s: e Zd ZdZd
dd�Zdd� Zdd� Zd d
� Zd d � ZdS )�MonitorObservera`
An asynchronous observer for device events.
This class subclasses :class:`~threading.Thread` class to asynchronously
observe a :class:`Monitor` in a background thread:
>>> from pyudev import Context, Monitor, MonitorObserver
>>> context = Context()
>>> monitor = Monitor.from_netlink(context)
>>> monitor.filter_by(subsystem='input')
>>> def print_device_event(device):
... print('background event {0.action}: {0.device_path}'.format(device))
>>> observer = MonitorObserver(monitor, callback=print_device_event, name='monitor-observer')
>>> observer.daemon
True
>>> observer.start()
In the above example, input device events will be printed in background,
until :meth:`stop()` is called on ``observer``.
.. note::
Instances of this class are always created as daemon thread. If you do
not want to use daemon threads for monitoring, you need explicitly set
:attr:`~threading.Thread.daemon` to ``False`` before invoking
:meth:`~threading.Thread.start()`.
.. seealso::
:attr:`Device.action`
The action that created this event.
:attr:`Device.sequence_number`
The sequence number of this event.
.. versionadded:: 0.14
.. versionchanged:: 0.15
:meth:`Monitor.start()` is implicitly called when the thread is started.
Nc s� |dkr� dkrt d��n|dk r2� dk r2t d��tj| f|�|� || _d| _d| _� dk r~ddl}|jdt� � fdd�}|| _ dS ) a
Create a new observer for the given ``monitor``.
``monitor`` is the :class:`Monitor` to observe. ``callback`` is the
callable to invoke on events, with the signature ``callback(device)``
where ``device`` is the :class:`Device` that caused the event.
.. warning::
``callback`` is invoked in the observer thread, hence the observer
is blocked while callback executes.
``args`` and ``kwargs`` are passed unchanged to the constructor of
:class:`~threading.Thread`.
.. deprecated:: 0.16
The ``event_handler`` argument will be removed in 1.0. Use
the ``callback`` argument instead.
.. versionchanged:: 0.16
Add ``callback`` argument.
Nzcallback missingz$Use either callback or event handlerTr zL"event_handler" argument will be removed in 1.0. Use Monitor.poll() instead.c s � | j | �S )N)r7 )�d)�
event_handlerr r �<lambda>� s z*MonitorObserver.__init__.<locals>.<lambda>)
r r r r Zdaemon� _stop_eventr& r' r( � _callback)r r rC �callback�args�kwargsr& r )rC r r � s
zMonitorObserver.__init__c C s" | j � stjj� | _tj| � dS )zStart the observer thread.N)Zis_aliver ZPipe�openrE r r) )r r r r r) � s zMonitorObserver.startc C s� | j j� tjj| j df| jjdf�}x�x�t|j�D ]x\}}|| jjj� kr\| jjj � d S || j j� kr�|dkr�t
t| j jdd�}x&t |d �D ]}| j |� q�W q4t
d��q4W q(W d S )Nr2 r )r6 zObserved monitor hung up)r r) r r4 r5 rE r r r �closer �iterrF r )r ZnotifierZfile_descriptorZeventZ read_devicer8 r r r �run s
zMonitorObserver.runc
C sB | j dkrdS | j j�" t| j jjd� | j jj� W dQ R X dS )aT
Send a stop signal to the background thread.
The background thread will eventually exit, but it may still be running
when this method returns. This method is essentially the asynchronous
equivalent to :meth:`stop()`.
.. note::
The underlying :attr:`monitor` is *not* stopped.
N� )rE Zsinkr �write�flush)r r r r � send_stop s
zMonitorObserver.send_stopc C s. | j � y | j� W n tk
r( Y nX dS )a
Synchronously stop the background thread.
.. note::
This method can safely be called from the observer thread. In this
case it is equivalent to :meth:`send_stop()`.
Send a stop signal to the backgroud (see :meth:`send_stop`), and waits
for the background thread to exit (see :meth:`~threading.Thread.join`)
if the current thread is *not* the observer thread.
After this method returns in a thread *that is not the observer
thread*, the ``callback`` is guaranteed to not be invoked again
anymore.
.. note::
The underlying :attr:`monitor` is *not* stopped.
.. versionchanged:: 0.16
This method can be called from the observer thread.
N)rQ �join� RuntimeError)r r r r �stop* s
zMonitorObserver.stop)NN) r; r< r= r> r r) rM rQ rT r r r r rA � s (
(rA )r> Z
__future__r r r r r+ r/ Z threadingr � functoolsr Z
pyudev.devicer Z pyudev._utilr r
Z
pyudev._osr r �objectr
rA r r r r �<module> s
Hacked By AnonymousFox1.0, Coded By AnonymousFox