From 88e775bf263260736b416158fa5c27bece8644c0 Mon Sep 17 00:00:00 2001 From: root Date: Wed, 28 Nov 2007 18:29:29 +0000 Subject: *** empty log message *** --- ev.3 | 3 +++ ev.html | 4 +++- ev.pod | 3 +++ 3 files changed, 9 insertions(+), 1 deletion(-) diff --git a/ev.3 b/ev.3 index 9313383..9e1c613 100644 --- a/ev.3 +++ b/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 diff --git a/ev.html b/ev.html index c153869..6c59bec 100644 --- a/ev.html +++ b/ev.html @@ -6,7 +6,7 @@ - + @@ -1250,6 +1250,8 @@ not exist" is a status change like any other. The condition "path does not exist" is signified by the 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 should be absolute and 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 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 diff --git a/ev.pod b/ev.pod index e906947..aaf225d 100644 --- a/ev.pod +++ b/ev.pod @@ -1225,6 +1225,9 @@ not exist" is signified by the C 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 be absolute and I 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 regularly on the path to see if it changed somehow. You can specify a recommended polling interval for this case. If you specify -- cgit v1.2.3