+ hRcsRt^RIt^RIt^RIHt^RIHt^RIHtH t ^RI H t H t ^RI Ht!RR4t!R R ]4tR#) zu pyudev.monitor ============== Monitor implementation. .. moduleauthor:: Sebastian Wiesner N)partial)Thread)pipepoll)eintr_retry_callensure_byte_string)Devicecsa]tRt^&toRtRtRt]RRl4t] R4t Rt RRlt R t R tR tR tR tRtRRltRtRtRtVtR#)Monitora 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 ` 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. csNWnW nVPVnRVnR#)FN)context_as_parameter__libudev_started)selfrZ monitor_p&&&3/usr/lib/python3.14/site-packages/pyudev/monitor.py__init__ZMonitor.__init__Ns! '((  cs<VPPV4R#N)r Zudev_monitor_unrefr &r__del__ZMonitor.__del__Ts ((.rc sVR9d\RPV44hVPPV\ V44pV'g \ R4hV!W4#)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. z8Invalid source: {0!r}. Must be one of "udev" or "kernel"zCould not create udev monitor)Zkerneludev) ValueErrorZformatr Zudev_monitor_new_from_netlinkrEnvironmentError)Zclsrsourcemonitors&&& r from_netlinkZMonitor.from_netlinkWsg. + +$fVn ""@@ '/ "#BC C7$$rc sVP#)z| ``True``, if this monitor was started, ``False`` otherwise. Readonly. .. seealso:: :meth:`start()` .. versionadded:: 0.16 )r rrrstartedZMonitor.startedzs}}rc s8VPPV4#)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_fdrrrfilenoZMonitor.filenos}}0066rNc s\V4pVe \V4pVPPWV4VPPV4R#)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)rr Z/udev_monitor_filter_add_match_subsystem_devtypeudev_monitor_filter_update)r Z subsystemZ device_typer r filter_byZMonitor.filter_bysI('y1  ",[9K EE [  006rc sVPPV\V44VPPV4R#)a 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_tagrr)r Ztag&&r filter_by_tagZMonitor.filter_by_tags1& 77>PQT>UV 006rc srVPPV4VPPV4R#)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_removerrrr remove_filterZMonitor.remove_filters(" 006 006rc sZ^RIpVPR\4VP4R#)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. Nz4Will be removed in 1.0. Use Monitor.start() instead.)warningswarnDeprecationWarningstart)r r"s& renable_receivingZMonitor.enable_receivings$"  BDV  rc sVP'gJVPPV4\P!V\ P 4RVnR#R#)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 Zudev_monitor_enable_receivingrZset_fd_status_flagosZ O_NONBLOCKrrrr%Z Monitor.starts?"}}} MM 7 7 =  # #D"-- 8 DM rc s<VPPW4R#)a 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 Zsizerrset_receive_buffer_sizeZMonitor.set_receive_buffer_sizes2 ::4Frc sXVPPV4pV'd\VPV4#R# \dapTP \ P \ P39dRp?R#TP \ P8XdRp?KhRp?ii;i)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_devicerrrerrnoZEAGAINZ EWOULDBLOCKZEINTR)r Zdevice_pZerror& r_receive_deviceZMonitor._receive_devices| ==DDTJ9AvdllH5KtK# ;;5<<1B1B"CC[[EKK/ s)">>> B) /B$>B$#B$$B)c sVeV^8d\VR,4pVP4\\PP VR34PV4'dVP 4#R#)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 Nir)Zintr%rrPoll for_eventsr+)r timeoutrrrZ Monitor.poll2s`X  7Q;'D.)G DII00$=BBG L L'') )rc sr^RIpVPR\4VP4pVPV3#)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. Nz3Will be removed in 1.0. Use Monitor.poll() instead.)r"r#r$ractionr r"devicer*rreceive_deviceZMonitor.receive_devicefs6B  ACU }}f$$rc# s"^RIpVPR\4VP4VP 4pVfKVP V3xK)5i)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`. NzuWill be removed in 1.0. Use an explicit loop over "poll()" instead, or monitor asynchronously with "MonitorObserver".)r"r#r$r%rr0r1r*r__iter__ZMonitor.__iter__sN&   !   YY[F!mmV++s =AA)r r r r)rr)__name__ __module__ __qualname____firstlineno____doc__rrZ classmethodrZpropertyrrrr r!r&r%r(r+rr3r4__static_attributes____classdictcell__Z __classdict__@rrr&s}%N / % %D7787,7(0!.G6*2h'%R,,rrcsFa]tRtRtoRtR RltRtRtRtRt R t Vt R#) MonitorObserveria 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 saVfSf \R4hVeSe \R4h\P!V.VO5/VBWnRVnRVnSe!^RIpVPR\4V3RlpW0n R#)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 handlerTzL"event_handler" argument will be removed in 1.0. Use Monitor.poll() instead.cs*<S!VPV4#r)r0)Zd event_handlers&rZZ*MonitorObserver.__init__..sqxx!;r) rrrrdaemon _stop_eventr"r#r$ _callback)r rr?ZcallbackZargsZkwargsr"s&&f&*, rrZMonitorObserver.__init__s0   5/0 0  !m&?CD D.t.v.    $  MM."  r>s+'R,"\ G**&rr>)r9r)r'Z functoolsrZ threadingrZ pyudev._osrrZ pyudev._utilrrZ pyudev.devicerrr>)rrrFs>" "= H,H,V bfbr