|
From: | Karsten Hilbert |
Subject: | Re: [Gnumed-devel] using cryptmount for postgresql cluster instance |
Date: | Tue, 12 Dec 2006 14:12:43 +0100 |
User-agent: | Mutt/1.5.13 (2006-08-11) |
The bootstrapper now supports alternate locations for databases. Just define alternate location = under the appropriate database section in the config file. For example: [database gnumed] name = gnumed_v3 alternate location = PGDATA2_GNUMED_V3 PGDATA2_GNUMED_V3 must be known to the PostgreSQL server as an environment variable. If you follow the steps in the PG manual > > http://www.postgresql.org/docs/7.4/static/manage-ag-alternate-locs.html and put the alternate location onto a cryptmount as described by Syan you should end up with a transparently filesystem-level encrypted database. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
[Prev in Thread] | Current Thread | [Next in Thread] |