Recently a Continuent Customer Asked: Part 1

The Question

"I have a cron job running as a non-tungsten user, and that job needs access to the tungsten-owned files under /opt/continuent, but cannot access the files it needs - how do I give access to those files to my cron job?"

The Answer

The tungsten-owned files are created specifically so that others cannot read them for security purposes, because these files often contain sensitive information.

The easiest way is to add that cron user to the tungsten group. For example, the lab install of /opt/continuent/tungsten/ looks like this, which shows that the tungsten group has read permissions:

drwxr-x---  8 tungsten tungsten 	84 Jun 10 21:02 cluster-home
-rw-r-----  1 tungsten tungsten  31516 Jun 10 21:02 EULA.txt
-rw-r-----  1 tungsten tungsten	583 Jun 10 21:02 INSTALL
-rw-r-----  1 tungsten tungsten	718 Nov  1 13:23 INSTALLED.tmpl
-rwxr-xr-x  1 tungsten tungsten	661 Nov  1 13:23 INSTALLED_USER_VALUES.sh
-rw-r-----  1 tungsten tungsten 402124 Jun 10 21:02 open_source_licenses.txt
drwxr-x---  8 tungsten tungsten   4096 Nov  8 20:46 tools
-rw-r-----  1 tungsten tungsten  29992 Nov  1 13:23 tungsten.cfg
-rw-rw-r--  1 tungsten tungsten 332458 Nov  1 13:24 tungsten-configure.log
drwxr-x--- 10 tungsten tungsten	100 Jun 10 21:02 tungsten-connector
drwxr-x--- 14 tungsten tungsten	165 Jun 10 21:02 tungsten-manager
drwxr-x--- 12 tungsten tungsten	156 Jun 10 21:02 tungsten-replicator

Members of the tungsten group already have read access, so any user added to the tungsten group would have read access to all files.

Wrap-Up

In this post we explored how to give read access to tungsten-owned files under the /opt/continuent/ directory by adding those users to the tungsten group.

Smooth sailing!