You can't just mount a filesystem and run a command to determine what the quota is, as set by the box the filesystem
is from. That's not how things work.
If you want to know the quota stats of user A on box B of
filesystem C, you need to be on box B. Mounting filesystem C
on system D isn't going to give you the answer.
However, I don't see what this has to do with Perl.
Abigail | [reply] |
Abigail the perl portion of this is weather to use a small perl server i.e. Net::TCP::Server or some other varriant of a mod to bind to a port on the NFS server and listen for incoming requests for a quota check on a specfic user. This is where I get confused cause I am not exactly sure how to make this wrk correctly and feed back the info I get to the web server which is running on a Linux box. I hope this helps clear up any confusion as to what I am indeed asking for advice on.
| [reply] |
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.)
| [reply] |
| [reply] |
I have tried the sudo method also and the biggest issue is that Linux and Solaris wont talk so this is why I need some sort of MOD or other small server that will listen on a certain port and then run the quota check.
| [reply] |
what do you mean by Solaris and Linux will not talk? Take a look under abigail's post to see what I would do instead of a homebrew service running on the nfs server. pushing the data out to a db from cron opens less of a hole on the nfs server than a homebrew tcp server.
| [reply] |
| [reply] |
hmm a T3 is a storage device not a server.... | [reply] |