From: Jeff Layton <jlayton@primarydata.com>
To: linux-nfs@vger.kernel.org
Subject: [nfs-utils RFC PATCH 2/7] nfsdcltrack: update comments in sqlite.c
Date: Fri, 15 Aug 2014 10:45:10 -0400 [thread overview]
Message-ID: <1408113915-5573-3-git-send-email-jlayton@primarydata.com> (raw)
In-Reply-To: <1408113915-5573-1-git-send-email-jlayton@primarydata.com>
Clean up and fix some inaccuracies.
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
---
utils/nfsdcltrack/sqlite.c | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/utils/nfsdcltrack/sqlite.c b/utils/nfsdcltrack/sqlite.c
index bac678980938..352f029d55c0 100644
--- a/utils/nfsdcltrack/sqlite.c
+++ b/utils/nfsdcltrack/sqlite.c
@@ -21,17 +21,15 @@
* Explanation:
*
* This file contains the code to manage the sqlite backend database for the
- * clstated upcall daemon.
+ * nfsdcltrack usermodehelper upcall program.
*
* The main database is called main.sqlite and contains the following tables:
*
* parameters: simple key/value pairs for storing database info
*
- * clients: one column containing a BLOB with the as sent by the client
- * and a timestamp (in epoch seconds) of when the record was
- * established
- *
- * FIXME: should we also record the fsid being accessed?
+ * clients: an "id" column containing a BLOB with the long-form clientid as
+ * sent by the client, a "time" column containing a timestamp (in
+ * epoch seconds) of when the record was last updated.
*/
#ifdef HAVE_CONFIG_H
--
1.9.3
next prev parent reply other threads:[~2014-08-15 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 14:45 [nfs-utils RFC PATCH 0/7] nfs-utils: support for lifting grace period early Jeff Layton
2014-08-15 14:45 ` [nfs-utils RFC PATCH 1/7] sm-notify: inform the kernel if there were no hosts to notify Jeff Layton
2014-08-15 14:45 ` Jeff Layton [this message]
2014-08-15 14:45 ` [nfs-utils RFC PATCH 3/7] nfsdcltrack: rename CLD_* constants with CLTRACK_* prefixes Jeff Layton
2014-08-15 14:45 ` [nfs-utils RFC PATCH 4/7] nfsdcltrack: overhaul database initializtion Jeff Layton
2014-08-15 14:45 ` [nfs-utils RFC PATCH 5/7] nfsdcltrack: update schema to v2 Jeff Layton
2014-08-15 14:45 ` [nfs-utils RFC PATCH 6/7] nfsdcltrack: grab the client minorversion from the env var if it's present Jeff Layton
2014-08-15 14:45 ` [nfs-utils RFC PATCH 7/7] nfsdcltrack: fetch NFSDCLTRACK_GRACE_START out of environment Jeff Layton
2014-08-18 20:04 ` [nfs-utils RFC PATCH 0/7] nfs-utils: support for lifting grace period early J. Bruce Fields
2014-08-18 20:59 ` Jeff Layton
2014-08-19 14:49 ` Jeff Layton
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=1408113915-5573-3-git-send-email-jlayton@primarydata.com \
--to=jlayton@primarydata.com \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).