You could indeed set up a TCP client/server model. The server
could be stand alone, or be run from inetd. You could use a
model where you make a connection for reach request, or you
could have a permanent connection. You could use UDP for
communication as well. Or you could create a file or database
with all the quota information, which you update from the
NFS server once every hour/day/week/whatever, and consult from
the webserver side. Yet another possibility is to forget
the entire web thing, and have people just type 'quota' on
the box itself - after all, if they don't have access to the
box, it doesn't matter what their quota is.
That's a decision you have to make, and what is the right
decision depends on many things. But one thing that hardly
plays a role in which solution you are going to take is
the language in which the solution will be written.
Abigail (wondering why someone wants to make an HTTP request to box A, just to get the quota information on box B.)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
