-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathHACKING
More file actions
37 lines (29 loc) · 1.42 KB
/
HACKING
File metadata and controls
37 lines (29 loc) · 1.42 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Different path data types and variable names
============================================
pathname: An XDR array; pathname4.
component: A string with a single object name. Example: "doc".
unixpath: Example: "/dev/fd0"
pathcomps: A list of components. Example: ["doc", "README"]
The function nfs4lib.unixpath2comps translates a unixpath to pathcomps.
Misc
====
"object" is preferred over "file", when talking about nfs_ftype4's.
Test tree principle
===================
Initial tree content is created by test_tree_net.py. Earlier, the
script test_tree.py, which runs locally, was used. This method is not
used anymore, since it is not always possible to run an Python
interpreter locally. For example, NetApp Filers are only accessible
via the network.
Test cases may create additional objects, but should use the tmp
directory. Test cases need not to delete created objects; failed test
cases are unable to do so anyway. Instead, test cases creating objects
should remove the object in question before trying the creation.
The test suite uses uid=0 and gid=0 when testing. The reason for this
is that root privilegies is required to create special device files,
for example. If your server uses root_squashing, tests may fail.
Test case preparation failure
=============================
If the preparation for a test case (such as creating a directory in
preparation for testing REMOVE) fails, the test case should be skipped
with a warning.