From: Andreas Schwab <schwab@suse.de>
To: Neal Becker <ndbecker2@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can/should inotify support fcntl?
Date: Thu, 27 Oct 2005 17:13:19 +0200 [thread overview]
Message-ID: <jepsprxab4.fsf@sykes.suse.de> (raw)
In-Reply-To: <djqmvc$64g$1@sea.gmane.org> (Neal Becker's message of "Thu, 27 Oct 2005 10:07:41 -0400")
Neal Becker <ndbecker2@gmail.com> writes:
> I'm trying to wrap inotify functionality for python. I ran into a problem.
> In order to use python's select on the fd, I need to use python's
> os.fdopen. It seems os.fdopen calls:
>
> fcntl(4, F_GETFL) = -1 EBADF (Bad file descriptor)
>
> Looks like inotify doesn't support calling fcntl. Should it?
F_GETFL is implemented in the VFS, and it can only fail if the fd does not
denote a valid file handle.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2005-10-27 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 14:07 can/should inotify support fcntl? Neal Becker
2005-10-27 15:13 ` Andreas Schwab [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=jepsprxab4.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ndbecker2@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.