hi,
YAMAMOTO Takashi y...@mwd.biglobe.ne.jp wrote:
if it trapped forever, it's a bug and should be fixed. my point was
that your change didn't fix the bug. blocking ioflush is merely a symptom.
The problem with userland filesystems is that we may have little control
as theses may be
On Wed, Oct 12, 2011 at 06:02:05AM +, YAMAMOTO Takashi wrote:
One way to fix that may be to have one ioflush thread for each userland
filesystem. That way a broken filesystem will not prevent ioflush from
working for others.
sure, it can be a good idea.
I have a patch that does
On Wed, Oct 12, 2011 at 12:39:48PM -0400, Christos Zoulas wrote:
Module Name: src
Committed By: christos
Date: Wed Oct 12 16:39:48 UTC 2011
Modified Files:
src/external/bsd/cron/dist: cron.8 database.c pathnames.h
Log Message:
process files in /etc/cron.d/
Not that I see
In article 20111012181619.GA24188@marx.bitnet,
Jukka Ruohonen jruoho...@iki.fi wrote:
On Wed, Oct 12, 2011 at 12:39:48PM -0400, Christos Zoulas wrote:
Module Name: src
Committed By:christos
Date:Wed Oct 12 16:39:48 UTC 2011
Modified Files:
On Wed, Oct 12, 2011 at 12:39:48PM -0400, Christos Zoulas wrote:
Module Name: src
Committed By: christos
Date: Wed Oct 12 16:39:48 UTC 2011
Modified Files:
src/external/bsd/cron/dist: cron.8 database.c pathnames.h
Log Message:
process files in /etc/cron.d/
If we're
On Wed, Oct 12, 2011 at 12:39:48PM -0400, Christos Zoulas wrote:
Modified Files:
src/external/bsd/cron/dist: cron.8 database.c pathnames.h
Log Message:
process files in /etc/cron.d/
For the record, I object to this change. I think keeping /etc small
and simple, and having one
