lkml.org 
[lkml]   [1998]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC] /proc/fs/nfsd/exports
Date
From


>>>H.J. Lu said:
> >
> > I am adding a proc file to kernel nfsd to display the exports and would
> > like opions on what its output should look like.
> >
> > The basic layout is
> >
> > path client flags IPs
> >
> > This is simular to the /etc/exports file, with the addition of the IP numb
ers
> > that client refers to.
> >
> > if myhost = 1.0.0.1 and 2.0.0.1
> > and if the etc/export file contained:
> >
> > /home myhost(async, ro, root_squash)
> > /home 2.0.0.1(async, rw, no_root_quash)
> >
> > /proc/fs/nfsd/exports would have:
> >
> > /home myhost 15 01000001,-02000001
> > /home 2.0.0.1 10 02000001
> >
> > or
> >
> > /home localhost(async,ro,root_squash) # 1.0.0.1,(2.0.0.1)
> > /home 2.0.0.1(async) # 2.0.0.1
> >
> >
> > The `myhost' export has its 2.0.0.1 IP _masked_ by the `2.0.0.1' export.
> > This is what the `-' or `()'s are trying to signify.
> >
>
> What do you meany "its 2.0.0.1 IP _masked_ by the `2.0.0.1' export"?
> BTW, I'd like to see the IP number in hex and the host order.

There is a hash of IP #s that point to a client. If two clients have
the same IP # then one will mask the other. A client is just an identifing
string.

It does not really matter to me how the IP are displayed. I may make it
selectable. I do think that if IP #s are displayed as HEX there must be a
standard. As all IP #s are displayed in net order now. It would be hard
to have nfs's in host order is /proc/net stays in net order.

I do hope that the output will be compatable with the xtab file.

Allen

---------------------------------
G. Allen Morris III
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:45    [from the cache]
©2003-2011 Jasper Spaans