Browse Source

*** empty log message ***

master rel-1.5
Marc Alexander Lehmann 14 years ago
parent
commit
a1dc90e83d
  1. 3
      ev.3
  2. 4
      ev.html
  3. 3
      ev.pod

3
ev.3

@ -1386,6 +1386,9 @@ not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (
otherwise always forced to be at least one) and all the other fields of
the stat buffer having unspecified contents.
.PP
The path \fIshould\fR be absolute and \fImust not\fR end in a slash. If it is
relative and your working directory changes, the behaviour is undefined.
.PP
Since there is no standard to do this, the portable implementation simply
calls \f(CW\*(C`stat (2)\*(C'\fR regularly on the path to see if it changed somehow. You
can specify a recommended polling interval for this case. If you specify

4
ev.html

@ -6,7 +6,7 @@
<meta name="description" content="Pod documentation for libev" />
<meta name="inputfile" content="&lt;standard input&gt;" />
<meta name="outputfile" content="&lt;standard output&gt;" />
<meta name="created" content="Wed Nov 28 18:32:11 2007" />
<meta name="created" content="Wed Nov 28 19:29:25 2007" />
<meta name="generator" content="Pod::Xhtml 1.57" />
<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
<body>
@ -1250,6 +1250,8 @@ not exist&quot; is a status change like any other. The condition &quot;path does
not exist&quot; is signified by the <code>st_nlink</code> field being zero (which is
otherwise always forced to be at least one) and all the other fields of
the stat buffer having unspecified contents.</p>
<p>The path <i>should</i> be absolute and <i>must not</i> end in a slash. If it is
relative and your working directory changes, the behaviour is undefined.</p>
<p>Since there is no standard to do this, the portable implementation simply
calls <code>stat (2)</code> regularly on the path to see if it changed somehow. You
can specify a recommended polling interval for this case. If you specify

3
ev.pod

@ -1225,6 +1225,9 @@ not exist" is signified by the C<st_nlink> field being zero (which is
otherwise always forced to be at least one) and all the other fields of
the stat buffer having unspecified contents.
The path I<should> be absolute and I<must not> end in a slash. If it is
relative and your working directory changes, the behaviour is undefined.
Since there is no standard to do this, the portable implementation simply
calls C<stat (2)> regularly on the path to see if it changed somehow. You
can specify a recommended polling interval for this case. If you specify

Loading…
Cancel
Save