mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jim <jimd@starshine.org>
To: linux-kernel@vger.kernel.org
Subject: Jiffies from userspace
Date: Fri, 1 Feb 2002 12:33:21 -0800	[thread overview]
Message-ID: <20020201123321.A799@mars.starshine.org> (raw)


 Sorry if this question seems stupid, but would this be a 
 reasonable way to get an estimate of the "current" value of the 
 kernel's jiffies:

 	set -- `cat /proc/self/stat`; echo ${22}

 ... my reasoning:

 The cat will start a new process, field 22? of its "stat" node 
 under proc should have the jiffies value at the time the process
 was started; so the echo command execute "shortly" thereafter.

 But am I right about the struct of stat:  Is that really in ${22}?

 (I'm not actually planning on using this technique, it's just a
  curiosity.  The only practical use I can see for it might be for 
  doing a sanity check on gettime; checking this for an increasing 
  value has a hedge against settime discontinuities).

 knfsd: follow symlinks?

 Also, an unrelated question:  is there a way to get the knfsd to
 resolve symlinks on the server side?  (Basically to configure it
 such that it doesn't present symlinks on the underlying fs as 
 symlinks to the client --- but rather it internally follows them,
 and presents the target link/inode data to network clients).  ISTR
 that the older user nfsd used to have some option like that.
 (I realize this second question would be better posed as a separate
 message; oh well).

--
Jim Dennis 

             reply	other threads:[~2002-02-01 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 20:33 Jim [this message]
2002-02-01 20:58 ` Eli Carter
2002-02-01 21:01 ` Mark Zealey
2002-02-02 15:21 ` Athanasius

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=20020201123321.A799@mars.starshine.org \
    --to=jimd@starshine.org \
    --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®