From: Oded Maimon <oded.maimon@gmail.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS@lists.sourceforge.net
Subject: Re: nfs break
Date: Mon, 20 Jun 2005 00:31:26 +0200 [thread overview]
Message-ID: <42B5F23E.4050303@gmail.com> (raw)
In-Reply-To: <1119208054.11291.21.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>su den 19.06.2005 Klokka 20:37 (+0200) skreiv Oded Maimon:
>
>
>>Hi,
>>
>>is there any way to make nfs-client create more informative logs?
>>
>>somthing like levels of logs?
>>
>>
>
>The only logging that the current NFS client supports is the information
>provided by "nfsstat".
>
>It is also possible to enable selective debug tracing in the case of
>client bugs, but those traces were not designed with system
>administration in mind, and so are unlikely to be very useful.
>
>Cheers,
> Trond
>
>
>
>
thanks, that will be very helpful,
can you please tell me how can i enable the debug tracing, just to see
what i can get from that?
sorry about the previous HTML mail.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-06-19 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 18:37 nfs break Oded Maimon
2005-06-19 19:07 ` Trond Myklebust
2005-06-19 21:08 ` Oded Maimon
2005-06-19 21:15 ` Casey Allen Shobe
2005-06-20 12:07 ` Greg Bradner
2005-06-20 13:22 ` Trond Myklebust
2005-06-19 22:31 ` Oded Maimon [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=42B5F23E.4050303@gmail.com \
--to=oded.maimon@gmail.com \
--cc=NFS@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.