-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 15 May 2001 18:27, Peter Eisentraut wrote:
> Lamar Owen writes:
> > What's the opposition about?
> The /etc directory is for system configuration files. The
> $PGDATA/postgresql.conf file is a database cluster configuration file.
Which is part of the system. /etc/mail/aliases is only an email config, but
is system-wide. I have multiple bind instances running on my main server --
it was relatively easy to tell bind through named.conf where to find the
particular zone files for the private side (I run NAT here and must maintain
an inside global DNS as well as an inside local DNS), and it was just as easy
to tell named to use named.conf.private for the private DNS side. And all
those files reside in /etc/named and /etc/named.private.
> The RPM set only allows one database cluster per system, so it's
> appropriate to think of this database cluster as "the" system database
> cluster, and of the associated configuration file as "the" system
> configuration file. But since the RPM set creates this situation it is
> only fitting that the RPM set resolve this situation. For example, it
> would be trivial to symlink the file /var/lib/pgsql/data/postgresql.conf
> to somewhere in /etc.
I can resolve the RPM issues. But, since talk is being made of changing the
core behavior, I wanted to weigh in on what I'd like to see. I may not have
high expectations of what I am likely to actually see happen, but the hope IS
there. If the changes are shot down, I can still cope with the issue.
But symlinks aren't the fix, as this is not an RPM-only issue -- there are
more than just RPM users who might want an FHS-compliant installation with
the capacity for multiple postmasters.
- --
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7AqlW5kGGI8vV9eERAqHZAJ4lJW0ndi+0aSSu5GQu12yAPkEDvACg4w9u
VfLdVIODenUU1GL4K4kf9OU=
=OtDH
-----END PGP SIGNATURE-----
