Very interesting twist David, as always. Can you point me in a direction to
research automounter? Never heard of if before. I know about IP restricting
the shares.
David Boyes
<[EMAIL PROTECTED]
e.net> To
Sent by: Linux on [email protected]
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: Dynamically making NFS shares
available/unavailable
11/23/2005 09:45
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
> Mark Post wrote:
> > Adam's suggestion will certainly work, but I wouldn't
> bother. I would
> > make the NFS export available to the one IP address that will be
> > scanning it and forget about it.
>
> Could you reformulate the question, please?
The original question was how to selectively export filesystems via NFS to
an external system for processing (in this case, virus scanning, which is
CPU intensive) and then revoke the export when the external system is not
using them.
Adam's suggestion was to start and stop the NFS server process via cron.
Mark's refinement was to explicitly specify the system DNS name or IP
address in /etc/exports so that the NFS server would permit only that
system
to actually access the filesystems.
I would add one more refinement: use automounter on the client system doing
the virus scanning and Mark's suggestion in combination. That way, the file
systems are only mounted when in use, and a human being doesn't need to be
involved at all.
-- db
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
