From: Robert Love <rlove@rlove.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: bryanwilkerson@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: inotify 0.23 errno 28 (ENOSPC)
Date: Tue, 24 May 2005 12:55:39 -0400 [thread overview]
Message-ID: <1116953739.13324.42.camel@betsy> (raw)
In-Reply-To: <1116953555.6280.31.camel@laptopd505.fenrus.org>
On Tue, 2005-05-24 at 18:52 +0200, Arjan van de Ven wrote:
> why isn't this an rlimit instead ?
Definitely could be.
Since inotify is built as a driver, the sysfs entry made sense, and it
sure is easier to implement.
But I'd have no problem with an rlimit. We don't seem to add those
frequently, though.
Robert Love
prev parent reply other threads:[~2005-05-24 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 16:33 Bryan Wilkerson
2005-05-24 16:35 ` Robert Love
2005-05-24 16:52 ` Arjan van de Ven
2005-05-24 16:55 ` Robert Love [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1116953739.13324.42.camel@betsy \
--to=rlove@rlove.org \
--cc=arjan@infradead.org \
--cc=bryanwilkerson@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®