public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: maximilian attems <janitor@sternwelten.at>
To: sandeep chavan <sandy_pict@yahoo.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: How to access remote proc file system?
Date: Mon, 7 Jul 2003 12:12:12 +0200	[thread overview]
Message-ID: <20030707101212.GC7441@stallburg.dyndns.org> (raw)
In-Reply-To: <20040129143146.55518.qmail@web40706.mail.yahoo.com>

On Thu, 29 Jan 2004, sandeep chavan wrote:

>  Hi all. I am an enggineering student working on a 
> project distributed systems monitoring and management.
>  I want to ask u that how can i access /proc files
> from
>  remote machine? [..]

your posting seems a bit offtopic and more networking related,
you'll probably get more advises at debian-user or whatever 
user group.
nevertheless take a look at mrtg (google will help you)

regards maks


  reply	other threads:[~2004-01-29 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 14:31 How to access remote proc file system? sandeep chavan
2003-07-07 10:12 ` maximilian attems [this message]
2004-01-30  9:53 ` Jan Hudec

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=20030707101212.GC7441@stallburg.dyndns.org \
    --to=janitor@sternwelten.at \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandy_pict@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox