Resolution:
1. The runtime owner of the rv daemon processes (rvd or rvrd) is dependent on the following factors:

(a). If the root user starts the daemon binary then the daemon drops its privileges to "nobody" (UID=65534) automatically.

(b). If a normal user starts the binary, and the binary is setuid root, then it drops privileges to the user that started the binary.

(c). If a normal user starts the binary, and the binary is *NOT* a setuid root, then the daemon runs under the user that started the binary. The difference with the previous two cases is that in this case the daemon cannot perform any activities that require root privileges (for example setting the priority of the process at runtime, etc).

A typical installation would be to have a user for managing RV (e.g. tibuser), and having the “bin” directory of tibrv installation (as well as the directory where the store file and log file is located) writable to “tibuser”.  If the RV binaries have been installed as setuid root, and are run by tibuser, the RV daemon will drop its privilege to “tibuser”.

2. When rvd/rvrd is run as root, it drops privileges to the user nobody &ltUID=65534>. If the daemons are setuid root, then they drop privileges to the user that started them(with an exception if root start them, in which case it drops privileges to user nobody).

The directory, in which you intend to maintain the store file, should be writable to the user that starts the rvd/rvrd process.

This is a normal behavior, designed so for security reasons since RV6.5 release.  Below is the related information extracted from the RV release note:

***************************************
- Implemented security fix to ensure that, even when started from a
   root account, the rvd process's user and group ids are set to that of
   an unprivileged user immediately after setting the process' priority
   at startup.
***************************************
The nobody, nobody4 and noaccess accounts are for running software as no privileged user.