1HOARD(1)                                                              HOARD(1)
2
3
4

NAME

6       hoard - Hoard database front-end
7

SYNOPSIS

9       hoard [ -d ] [ -f source | cmds ]
10
11

DESCRIPTION

13       hoard  is  a  front-end to the hoard database (HDB) managed by the Coda
14       cache manager, Venus.  The HDB provides a means for users to explicitly
15       control  Venus  caching  behavior.  HDB entries specify the degree of a
16       users interest in particular file system objects.  Venus combines  this
17       information  with implicit knowledge that it has about file access pat‐
18       terns to try to keep the "best" set of objects  in  its  cache  at  all
19       times.   The  HDB is maintained in non-volatile storage, so it survives
20       Venus restarts and client reboots.
21
22       Users manipulate the HDB by issuing commands to the hoard program.  The
23       following hoard commands are currently recognized:
24
25       add filename attributes
26
27       clear uid
28
29       delete filename
30
31       list outfile uid
32
33       modify filename attributes
34
35       Hoard  distinguishes between children of a directory, which are members
36       of the directory, descendants which are either children or  descendants
37       of childres of the directory.
38
39       Commands may be abbreviated by their first letter.  Parameters in angle
40       brackets are optional, and have default  values  if  unspecified.   The
41       attributes parameter is specified as a string of options separated by :
42       characters.  The currently recognized options are:
43
44       1-1000 Assign this object the hoard priority indicated.
45
46       c      Current children of this directory will inherit its  hoard  sta‐
47              tus.
48
49       c+     Current  and  future children of this directory will inherit its
50              hoard status.
51
52       d      Current descendents of this directory  will  inherit  its  hoard
53              status.
54
55       d+     Current  and  future  descendents of this directory will inherit
56              its hoard status
57
58       If the uid in the clear and list commands is unspecified,  the  entries
59       of  all  users  are  cleared or listed respectively.  The default hoard
60       priority is 10.
61
62   EXAMPLE HOARD COMMAND FILE
63       clear
64       add /coda/project/coda/src 100:d+
65       add /coda/usr/jjk/.login   1000
66
67       Access to the hoard database is restricted in the following ways.   All
68       hoard  commands  fail  unless the hoard program is executed by the user
69       who is identified as the primary user in the  venus.conf  configuration
70       file.  If  no primary user is specified, special permission is given to
71       the console user who is logged in on the local (or first virtual)  con‐
72       sole. Primary users may add entries and access existing entries without
73       restriction. Other users may not add hoard entries, and they  may  only
74       clear, delete, list, or modify their own entries.
75
76       The command-line options are:
77
78       -d     Enables debugging output.
79
80       -f     Take commands from source. -f must be the last argument if spec‐
81              ified. An argument of - means, use stdin  as  the  source  file.
82              Source statements may be given directly on the command line (one
83              per line) by enclosing them in single quotes.
84

DIAGNOSTICS

86       Hoard copies command lines that it cannot parse to stderr. If a syntac‐
87       tically correct command is rejected by Venus, the corresponding pioctl,
88       its arguments, and the errno are copied to stderr.
89

BUGS

91       · Negative priorities should be allowed.
92

SEE ALSO

94       venus(8)
95

AUTHORS

97       · Jay Kistler, 1990, Created
98
99
100
101Coda Distributed File System     25 April 2005                        HOARD(1)