GT.M - Rock solid. Lightning fast. Secure. No compromises. On 09/07/2010 08:03 AM, Karsten Hilbert wrote:
On Mon, Sep 06, 2010 at 11:40:55PM -0400, K.S. Bhaskar wrote: > The concept of a "single user" GT.M is not meaningful. GT.M is > inherently multi-user. Well, one needs to keep apart the concepts. Of course, the database engine itself is (like PostgreSQL) inherently multi-(DB)-user and will always make it possible for several (DB)-users to connect if so configured. Nonetheless it need not be installed in a *systemwide* way but could conceivably also be installed in a way local to a specific *system* user and with system level file permissions restricted to said system account. Of course, even that instance will allow multiple DB users to access but from the point of view of the system user this is a single-user, "private", "local" installation -- all DB users semantically map to the one system user.
[KSB] The GT.M engine itself doesn't care where it is installed. A GT.M process requires that the $gtm_dist environment variable point to the directory where it is installed. Indeed, you can have the exact same version of GT.M installed in two locations in the file system, and they can operate completely independently of each other - the processes using each installation would have appropriate values of $gtm_dist, $gtm_log and $gtm_tmp.
Regards -- Bhaskar _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _____________