2 .TH RQUOTAD 8 "8 Mar 2001"
4 rquotad, rpc.rquotad \- remote quota server
6 .B /usr/etc/rpc.rquotad [-p " port "] "
9 .IX "rquotad daemon" "" "\fLrquotad\fP \(em remote quota server"
10 .IX daemons "rquotad daemon" "" "\fLrquotad\fP \(em remote quota server"
11 .IX "user quotas" "rquotad daemon" "" "\fLrquotad\fP \(em remote quota server"
12 .IX "disk quotas" "rquotad daemon" "" "\fLrquotad\fP \(em remote quota server"
13 .IX "quotas" "rquotad daemon" "" "\fLrquotad\fP \(em remote quota server"
14 .IX "file system" "rquotad daemon" "" "\fLrquotad\fP \(em remote quota server"
15 .IX "remote procedure call services" "rquotad" "" "\fLrquotad\fP \(em remote quota server"
19 server which returns quotas for a user of a local file system
20 which is mounted by a remote machine over the
22 The results are used by
24 to display user quotas for remote file systems.
28 daemon is normally started at boottime from the
30 script (on systems with BSD'ish scripts, e.g. Slackware), or from the
36 (on systems with SysV'ish scripts, e.g. RedHat, SuSE, etc).
40 .BI "\-p," "" " \-\-port " port
43 to listen on. By default,
47 to assign it a port number. As of this writing, there is not
48 a standard port number that
50 always or usually assigns. Specifying
51 a port may be useful when implementing a firewall.
53 .SH TCP_WRAPPERS SUPPORT
56 version is protected by the
58 library. You have to give the clients access to
60 if they should be allowed to use it. To allow connects from clients of
61 the .bar.com domain you could use the following line in /etc/hosts.allow:
65 You have to use the daemon name
67 for the daemon name (even if the binary has a different name). For the
68 client names you can only use the keyword ALL or IP addresses (NOT
69 host or domain names).
71 For further information please have a look at the
81 -- quota files locate in the file system's root