public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Gardner <rob.gardner@hp.com>
To: "\"Fábio Jr.\"" <fjuniorlista@gmail.com>
Cc: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: [NFS] Export especific file extension
Date: Tue, 28 Jul 2009 07:20:00 -0600	[thread overview]
Message-ID: <4A6EFB00.2080308@hp.com> (raw)
In-Reply-To: <4A6EDBC9.6040008@gmail.com>

=46=E1bio Jr. wrote:
> Rob Gardner escreveu:
>  =20
>> F=E1bio Jr. wrote:
>>    =20
>>> Hello all.
>>>
>>> Is there a way to export only some specific file extensions from a=20
>>> directory, like exporting only the files in /home/fabio with the .j=
pg=20
>>> extension?
>>>      =20
>> You could do this pretty easily by exporting a 'fuse' filesystem=20
>> layered on top of your home directory.
>>
>> Rob Gardner
>> HP
>>
>>    =20
> Thanks Rob for the reply,
>
> This means that if I use this FUSE, I can export via NFS only the fil=
e=20
> extension that I need? let me explain my problem, not really a proble=
m,=20
> but a doubt.
>
> I have one storage that have my aplication files. This storage is=20
> mounted via NFS in my 3 aplication servers. Now I will put another=20
> server, to serve only static files (jpg,png,css,js basically), and=20
> though that maybe there is a way to export only these files from the=20
> storage. The problem is that these files are not organized in diferen=
t=20
> folders.
>
> Maybe my first question doesn't explained my real necessity, but your=
=20
> answer will make me search a little more about FUSE.

I think your first question explained your need clearly. FUSE is a=20
filesystem layer that lets you filter requests through a user program=20
such as a python script. So, for instance, every time a process opens a=
=20
file, a function is called in your script, and you can look at the name=
=20
of the file being opened, and there decide whether or not to allow the=20
file to be opened. I think this would solve your problem easily. Though=
=20
all the storage is "exported", only files with certain names (ie, *.jpg=
,=20
etc) could be opened. You could also decide which files get enumerated=20
with readdir, etc.

Rob Gardner
HP


-----------------------------------------------------------------------=
-------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30=
-Day=20
trial. Simplify your report design, integration and deployment - and fo=
cus on=20
what you do best, core application coding. Discover what's new with=20
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs


  reply	other threads:[~2009-07-28 13:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 20:31 [NFS] Export especific file extension "Fábio Jr."
2009-07-27 22:20 ` Rob Gardner
2009-07-28 11:06   ` "Fábio Jr."
2009-07-28 13:20     ` Rob Gardner [this message]
2009-07-28 13:36       ` "Fábio Jr."
2009-07-28 13:53         ` Rob Gardner
2009-07-28 14:40           ` "Fábio Jr."
2009-07-28 15:58             ` Rob Gardner
2009-07-28 16:21               ` J. Bruce Fields

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=4A6EFB00.2080308@hp.com \
    --to=rob.gardner@hp.com \
    --cc=fjuniorlista@gmail.com \
    --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