Linux NFS development
 help / color / mirror / Atom feed
From: Michael <mogmios@mlug.missouri.edu>
To: nfs@lists.sourceforge.net
Subject: Re: auto-discovery of exports?
Date: Thu, 08 Apr 2004 03:29:37 -0700	[thread overview]
Message-ID: <40752991.6020402@mlug.missouri.edu> (raw)
In-Reply-To: <41089CB27BD8D24E8385C8003EDAF7AB08484E@karl.alexa.com>

Thanks everyone for the input. Based on your suggestions I quickly put 
together this rough shell script which seems to work. It correctly found 
every nfs server on my LAN and listed the exports each had.

---------------
#!/bin/bash

PORT='111'
NETWORK='192.168.1.0/24'

NMAP='/usr/bin/nmap'
SHOWMOUNT='/usr/sbin/showmount'

IPs=`$NMAP -PT$PORT $NETWORK | grep "Interesting ports on" | cut -d" " 
-f4 | cut -d":" -f1`

for IP in $IPs ; do
        $SHOWMOUNT -e $IP
done
---------------


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2004-04-08 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 23:01 auto-discovery of exports? Guolin Cheng
2004-04-08  0:37 ` Ian Kent
2004-04-08  5:34   ` Bryan O'Sullivan
2004-04-08 10:29 ` Michael [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-08  1:44 Guolin Cheng
2004-04-08  2:02 ` Greg Banks
2004-04-08  6:54   ` Olaf Kirch
2004-04-08  7:07     ` Greg Banks
2004-04-08  8:55       ` Olaf Kirch
2004-04-11  9:44         ` Greg Banks
2004-04-07  8:03 Michael

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=40752991.6020402@mlug.missouri.edu \
    --to=mogmios@mlug.missouri.edu \
    --cc=nfs@lists.sourceforge.net \
    /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