What are the meanings of the file attributes in Harvest? Why are they changed upon checkout, how are they stored in the database and what names are used for the UNIX groups?

Document ID : KB000055378
Last Modified Date : 14/02/2018
Show Technical Document Details


Q1) In the Harvest Workbench the Remote Agent Neighborhood shows 'vexvexvex', but in UNIX it shows as 'drwxrwsr-x'. Why the difference?

Q2) Harvest changes the write attribute for clear reasons as documented. However, it also changes other attributes like "s". Why and which rules are used in changing the other attributes besides the write attribute?

For example:

Check In directory attributes:

drwxrwsr-x 3 ipwho pos60t 512 Mar 29 13:41 huh/

After checkout:

drwxr-xr-x 2 ipwho pos60t 512 Mar 29 13:47 huh/

Q3) In the Repository, the file attributes are stored in the table HARVERSIONDATA in column FILEACCESS. However, there is no entry in this table for a directory. How can Harvest create the right attributes if they are not stored in the Repository? What rules are used for the attributes?

Q4) What rules are used during the checkout process to determine which names to be used for the groups? In the example above "ipwho" and "pos60t". It looks like the username is the Harvest agent userid, but what is used for the group id?


A1) This is how the agent code was originally designed to work, although the reasons for it are not documented any more. Basically the mapping is as follows:

r (read) -> v (view)
w (write) -> e (edit)
x (execute) is unchanged

A2) We do not store file attributes for directories. During checkout a directory will have 775 (drwxrwxr-x) permissions if 'shared working directory' is set and 755 (drwxr-xr-x) if 'shared working directory' is not set.

In Harvest r7.1 Patch 1, the file access for newly created directories and files will be restricted further by the shell's umask value.

A3) see A2) During checkout, a directory will be set to 775 (drwxrwxr-x) or 755 (drwxr-xr-x).

A4) The group setting should be the primary group associated with the checkout user.