John Polstra scribbled this message on Sep 12:
In article [EMAIL PROTECTED],
Garrett Wollman [EMAIL PROTECTED] wrote:
[POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE]
It is probably undocumented. I was a bit reluctant to document it
since I know that the interface is not correct. One
John-Mark Gurney wrote:
John Polstra scribbled this message on Sep 12:
Just to avoid duplicated effort: I currently have work in progress
on a "fslog" pseudo-device. It enables you to monitor a filesystem
and receive notifications for all interesting changes to files and
directories.
In message [EMAIL PROTECTED], John Polstra writes:
ugh, why aren't you extending poll to work on files and directories to
get this info?? it would make MUCH more sense to extend poll to do this..
any specific reason why it wasn't done this way?
Yes. Last time I checked, our CVS
In message [EMAIL PROTECTED] John Polstra writes:
: There are now 63000 files and directories in the repository.
: That's 2**3 * 3**2 * 5**3 * 7. If we concatenate the exponents,
: we get 3231, which is 3**2 * 359. Repeating, we get 21, which
: is 3 * 7. One more repetition and
In message [EMAIL PROTECTED], John Polstra writes:
ugh, why aren't you extending poll to work on files and directories to
get this info?? it would make MUCH more sense to extend poll to do this..
any specific reason why it wasn't done this way?
Yes. Last time I checked, our CVS
In message [EMAIL PROTECTED] John Polstra writes:
: My personal interest is to allow a CVSup master server to avoid
: doing a tree walk whenever a client connects. I want to provide the
: functionality of the old "supscan" utility, but in real time.
Also useful for tasty /dev/ persistance in a
In article [EMAIL PROTECTED],
Tony Finch [EMAIL PROTECTED] wrote:
Are there any standard APIs for doing file meta-operations
asynchronously? (open, close, creat, link, unlink, etc.)
I only know of one way to do that. Hand the operation off to a
separate process, using the FD-passing
In article [EMAIL PROTECTED],
Garrett Wollman [EMAIL PROTECTED] wrote:
[POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE]
It is probably undocumented. I was a bit reluctant to document it
since I know that the interface is not correct. One of these days,
I (or more likely some enterprising
In article [EMAIL PROTECTED],
Garrett Wollman [EMAIL PROTECTED] wrote:
[POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE]
It is probably undocumented. I was a bit reluctant to document it
since I know that the interface is not correct. One of these days,
I (or more likely some
On Sun, 12 Sep 1999 10:56:42 -0700 (PDT), John Polstra [EMAIL PROTECTED] said:
Just to avoid duplicated effort: I currently have work in progress
on a "fslog" pseudo-device. It enables you to monitor a filesystem
and receive notifications for all interesting changes to files and
Luigi Rizzo [EMAIL PROTECTED] writes:
Is there any way to guarantee (more or less strictly, see below)
that when i issue a read() on a file (a real file coming from a
UFS i mean) such read will not block because data from the disk is
not in memory yet, yet avoid that i end up in a busy
Hi,
please redirect to the appropriate forum if appropriate.
There is one thing i don't completely understand with non-blocking
FS operation.
Is there any way to guarantee (more or less strictly, see below)
that when i issue a read() on a file (a real file coming from a
UFS i mean) such read
The Posix AIO calls that john implememted are the best way of doing this.
On Thu, 9 Sep 1999, Luigi Rizzo wrote:
Hi,
please redirect to the appropriate forum if appropriate.
There is one thing i don't completely understand with non-blocking
FS operation.
Is there any way to
Date: Thu, 9 Sep 1999 16:18:57 +0200 (MET DST)
From: Luigi Rizzo [EMAIL PROTECTED]
Subject: An FS question perhaps... non blocking I/O.
[ ... snip ... ]
The app i have in mind is squid-like, which, if i understand
well, is a
single process looping around a select. If i get things
right
14 matches
Mail list logo
