diff options
Diffstat (limited to 'docstrings/pyinotify._SysProcessEvent-class.html')
| -rw-r--r-- | docstrings/pyinotify._SysProcessEvent-class.html | 88 |
1 files changed, 43 insertions, 45 deletions
diff --git a/docstrings/pyinotify._SysProcessEvent-class.html b/docstrings/pyinotify._SysProcessEvent-class.html index e88bfe5..f55baaf 100644 --- a/docstrings/pyinotify._SysProcessEvent-class.html +++ b/docstrings/pyinotify._SysProcessEvent-class.html @@ -55,27 +55,28 @@ </tr> </table> <!-- ==================== CLASS DESCRIPTION ==================== --> -<h1 class="epydoc">Class _SysProcessEvent</h1><span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent">source code</a></span><br /><br /> +<h1 class="epydoc">Class _SysProcessEvent</h1><p class="nomargin-top"><span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent">source code</a></span></p> <center> -<center> <map id="uml_class_diagram_for_pyinotif_24" name="uml_class_diagram_for_pyinotif_24"> -<area shape="rect" href="pyinotify._ProcessEvent-class.html#__repr__" title="repr(x)" alt="" coords="95,36,215,54"/> -<area shape="rect" href="pyinotify._ProcessEvent-class.html#__call__" title="To behave like a functor the object must be callable." alt="" coords="95,54,215,73"/> -<area shape="rect" href="pyinotify._ProcessEvent-class.html" title="Abstract processing event class." alt="" coords="93,10,216,74"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_IGNORED" title="The watch descriptor raised by this event is now ignored (forever), it can be safely deleted from watch manager dictionary." alt="" coords="17,129,292,148"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_default" title="Common handling for the following events:" alt="" coords="17,148,292,166"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_MOVE_SELF" title="STATUS: the following bug has been fixed in the recent kernels (fixme: which version ?)." alt="" coords="17,166,292,185"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_Q_OVERFLOW" title="Only signal overflow, most of the common flags are irrelevant for this event (path, wd, name)." alt="" coords="17,185,292,204"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_MOVED_FROM" title="Map the cookie with the source path (+ date for cleaning)." alt="" coords="17,204,292,222"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_CREATE" title="If the event concerns a directory and the auto_add flag of the targetted watch is set to True, a new watch is added on this new directory, with the same attributes's values than those of this watch." alt="" coords="17,222,292,241"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_MOVED_TO" title="Map the source path with the destination path (+ date for cleaning)." alt="" coords="17,241,292,260"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#cleanup" title="Cleanup (delete) old (>1mn) records contained in self._mv_cookie and self._mv." alt="" coords="17,260,292,278"/> -<area shape="rect" href="pyinotify._SysProcessEvent-class.html#__init__" title="x.__init__(...) initializes x; see x.__class__.__doc__ for signature" alt="" coords="17,278,292,297"/> +<center> <map id="uml_class_diagram_for_pyinotif_29" name="uml_class_diagram_for_pyinotif_29"> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#__init__" title="x.__init__(...) initializes x; see x.__class__.__doc__ for signature" alt="" coords="17,129,292,148"/> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#cleanup" title="Cleanup (delete) old (>1mn) records contained in self._mv_cookie and  self._mv." alt="" coords="17,148,292,166"/> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_CREATE" title="If the event concerns a directory and the auto_add flag of the targetted  watch is set to True, a new watch is added on this new directory, with the  same attributes's values than those of this watch." alt="" coords="17,166,292,185"/> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_MOVED_FROM" title="Map the cookie with the source path (+ date for cleaning)." alt="" coords="17,185,292,204"/> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_MOVED_TO" title="Map the source path with the destination path (+ date for cleaning)." alt="" coords="17,204,292,222"/> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_MOVE_SELF" title="STATUS: the following bug has been fixed in the recent kernels (fixme:  which version ?)." alt="" coords="17,222,292,241"/> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_Q_OVERFLOW" title="Only signal overflow, most of the common flags are irrelevant for this  event (path, wd, name)." alt="" coords="17,241,292,260"/> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_IN_IGNORED" title="The watch descriptor raised by this event is now ignored (forever), it can  be safely deleted from watch manager dictionary." alt="" coords="17,260,292,278"/> +<area shape="rect" href="pyinotify._SysProcessEvent-class.html#process_default" title="Common handling for the following events:" alt="" coords="17,278,292,297"/> <area shape="rect" href="pyinotify._SysProcessEvent-class.html" title="There is three kind of processing according to each event:" alt="" coords="16,104,293,298"/> +<area shape="rect" href="pyinotify._ProcessEvent-class.html#__call__" title="To behave like a functor the object must be callable." alt="" coords="95,36,215,54"/> +<area shape="rect" href="pyinotify._ProcessEvent-class.html#__repr__" title="repr(x)" alt="" coords="95,54,215,73"/> +<area shape="rect" href="pyinotify._ProcessEvent-class.html" title="Abstract processing event class." alt="" coords="93,10,216,74"/> </map> - <img src="uml_class_diagram_for_pyinotif_24.gif" alt='' usemap="#uml_class_diagram_for_pyinotif_24" ismap="ismap" class="graph-without-title" /> -</center></center> + <img src="uml_class_diagram_for_pyinotif_29.gif" alt='' usemap="#uml_class_diagram_for_pyinotif_29" ismap="ismap" class="graph-without-title" /> +</center> +</center> <hr /> -There is three kind of processing according to each event: +<p>There is three kind of processing according to each event:</p> <ol start="1"> <li> special handling (deletion from internal container, bug, ...). @@ -90,7 +91,7 @@ There is three kind of processing according to each event: event, he is not processed as the others events, instead, its value is captured and appropriately aggregated to dst event. </li> - </ol><br /><br /> + </ol> <!-- ==================== INSTANCE METHODS ==================== --> <a name="section-InstanceMethods"></a> @@ -118,8 +119,7 @@ There is three kind of processing according to each event: <td><span class="summary-sig"><a href="pyinotify._SysProcessEvent-class.html#__init__" class="summary-sig-name">__init__</a>(<span class="summary-sig-arg">self</span>, <span class="summary-sig-arg">wm</span>, <span class="summary-sig-arg">notifier</span>)</span><br /> - x.__init__(...) initializes x; see x.__class__.__doc__ for - signature</td> + x.__init__(...) initializes x; see x.__class__.__doc__ for signature</td> <td align="right" valign="top"> <span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent.__init__">source code</a></span> @@ -136,8 +136,8 @@ There is three kind of processing according to each event: <table width="100%" cellpadding="0" cellspacing="0" border="0"> <tr> <td><span class="summary-sig"><a name="cleanup"></a><span class="summary-sig-name">cleanup</span>(<span class="summary-sig-arg">self</span>)</span><br /> - Cleanup (delete) old (>1mn) records contained in - self._mv_cookie and self._mv.</td> + Cleanup (delete) old (>1mn) records contained in self._mv_cookie + and self._mv.</td> <td align="right" valign="top"> <span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent.cleanup">source code</a></span> @@ -194,8 +194,7 @@ There is three kind of processing according to each event: <tr> <td><span class="summary-sig"><a name="process_IN_MOVED_TO"></a><span class="summary-sig-name">process_IN_MOVED_TO</span>(<span class="summary-sig-arg">self</span>, <span class="summary-sig-arg">raw_event</span>)</span><br /> - Map the source path with the destination path (+ date for - cleaning).</td> + Map the source path with the destination path (+ date for cleaning).</td> <td align="right" valign="top"> <span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent.process_IN_MOVED_TO">source code</a></span> @@ -251,9 +250,8 @@ There is three kind of processing according to each event: <tr> <td><span class="summary-sig"><a href="pyinotify._SysProcessEvent-class.html#process_IN_IGNORED" class="summary-sig-name">process_IN_IGNORED</a>(<span class="summary-sig-arg">self</span>, <span class="summary-sig-arg">raw_event</span>)</span><br /> - The watch descriptor raised by this event is now ignored - (forever), it can be safely deleted from watch manager - dictionary.</td> + The watch descriptor raised by this event is now ignored (forever), + it can be safely deleted from watch manager dictionary.</td> <td align="right" valign="top"> <span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent.process_IN_IGNORED">source code</a></span> @@ -284,7 +282,7 @@ There is three kind of processing according to each event: </tr> <tr> <td colspan="2" class="summary"> - <p class="indent-wrapped-lines"><b>Inherited from <code><a href="pyinotify._ProcessEvent-class.html">_ProcessEvent</a></code></b>: + <p class="indent-wrapped-lines"><b>Inherited from <code><a href="pyinotify._ProcessEvent-class.html" onclick="show_private();">_ProcessEvent</a></code></b>: <code><a href="pyinotify._ProcessEvent-class.html#__call__">__call__</a></code>, <code><a href="pyinotify._ProcessEvent-class.html#__repr__">__repr__</a></code> </p> @@ -359,10 +357,10 @@ There is three kind of processing according to each event: </td><td align="right" valign="top" ><span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent.__init__">source code</a></span> </td> - </table> + </tr></table> - x.__init__(...) initializes x; see x.__class__.__doc__ for - signature + <p>x.__init__(...) initializes x; see x.__class__.__doc__ for + signature</p> <dl class="fields"> <dt>Parameters:</dt> <dd><ul class="nomargin-top"> @@ -370,7 +368,7 @@ There is three kind of processing according to each event: <li><strong class="pname"><code>notifier</code></strong> (Instance of Notifier.) - notifier.</li> </ul></dd> <dt>Overrides: - object.__init__ + object.__init__ </dt> </dl> </td></tr></table> @@ -388,15 +386,15 @@ There is three kind of processing according to each event: </td><td align="right" valign="top" ><span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent.process_IN_MOVE_SELF">source code</a></span> </td> - </table> + </tr></table> <p>STATUS: the following bug has been fixed in the recent kernels (fixme: which version ?). Now it raises IN_DELETE_SELF instead.</p> - Old kernels are bugged, this event is raised when the watched item was + <p>Old kernels are bugged, this event is raised when the watched item was moved, so we must update its path, but under some circumstances it can be impossible: if its parent directory and its destination directory aren't watched. The kernel (see include/linux/fsnotify.h) doesn't bring us - enough informations like the destination path of moved items. + enough informations like the destination path of moved items.</p> <dl class="fields"> </dl> </td></tr></table> @@ -414,12 +412,12 @@ There is three kind of processing according to each event: </td><td align="right" valign="top" ><span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent.process_IN_IGNORED">source code</a></span> </td> - </table> + </tr></table> - The watch descriptor raised by this event is now ignored (forever), it + <p>The watch descriptor raised by this event is now ignored (forever), it can be safely deleted from watch manager dictionary. After this event we can be sure that neither the event queue neither the system will raise an - event associated to this wd. + event associated to this wd.</p> <dl class="fields"> </dl> </td></tr></table> @@ -438,11 +436,11 @@ There is three kind of processing according to each event: </td><td align="right" valign="top" ><span class="codelink"><a href="pyinotify-pysrc.html#_SysProcessEvent.process_default">source code</a></span> </td> - </table> + </tr></table> <p>Common handling for the following events:</p> - IN_ACCESS, IN_MODIFY, IN_ATTRIB, IN_CLOSE_WRITE, IN_CLOSE_NOWRITE, - IN_OPEN, IN_DELETE, IN_DELETE_SELF, IN_UNMOUNT. + <p>IN_ACCESS, IN_MODIFY, IN_ATTRIB, IN_CLOSE_WRITE, IN_CLOSE_NOWRITE, + IN_OPEN, IN_DELETE, IN_DELETE_SELF, IN_UNMOUNT.</p> <dl class="fields"> </dl> </td></tr></table> @@ -474,10 +472,11 @@ There is three kind of processing according to each event: <table border="0" cellpadding="0" cellspacing="0" width="100%%"> <tr> <td align="left" class="footer"> - Generated by Epydoc 3.0beta1 on Sun Aug 10 13:37:39 2008 + Generated by Epydoc 3.0.1 on Tue Jan 6 22:57:24 2009 </td> <td align="right" class="footer"> - <a href="http://epydoc.sourceforge.net">http://epydoc.sourceforge.net</a> + <a target="mainFrame" href="http://epydoc.sourceforge.net" + >http://epydoc.sourceforge.net</a> </td> </tr> </table> @@ -488,9 +487,8 @@ There is three kind of processing according to each event: // javascript is turned off then we want them to be // visible); but by default, we want to hide them. So hide // them unless we have a cookie that says to show them. - checkCookie() + checkCookie(); // --> </script> - </body> </html> |