I've resolved my issue, but I do think there is a bug here. It seems
the SELECT, INSERT, UPDATE, DELETE permissions are all the management
node's database user requires. However, even though there is a
parameter in /etc/vcl/vcld.conf for LockerWrtUser, the value the
management node will
The recommended permissions for the vcl user on the backend are correct
(SELECT, INSERT, UPDATE, DELETE). Also it's probably not good to have
anything remotely accessing your database with All Privileges - just from a
security perspective. At some-point in the future we would like to moved to
Could you re-phrase this part? I don't understand what issue your
highlighting?
The value assigned to 'LockerWrtUser=' is the variable used when vcld
starts to make the database connection.
Aaron
--On April 6, 2009 12:35:26 PM -0400 Brian Bouterse bmbou...@ncsu.edu
wrote:
I've resolved
Even though LockerWrtUser is there to indicate which database user the
management node should use to login to the db, the only value the
daemon will start with is vcl. Has anyone ever gotten the vcld to
start successfully and checkin with the database when using something
other than 'vcl'
Yes - we are using different names for the value LockerWrtUser=. Actually
we have several vcl-wrt vcl-wcu, vcl-dev, etc
This is defined when adding the user to the database. From the install
instructions file under step 2.
2) create a user with SELECT, INSERT, UPDATE, and DELETE privileges
BTW - what username are trying to use besides 'vcl'. It's possible there is
a bug in the portion that is parsing vcld.conf and it's not picking up
specific characters.
Aaron
