Excerpts from Philip Brown's message of Thu Jun 18 20:47:22 -0400 2009: > Lest anyone misunderstand me, i will reiterate that I am still > completely in favour of the DEFAULT for demons and things, being > "configs go in /etc/opt/csw".
Understood. > You can just NFS-share out /opt/csw everywhere, and it will work > correctly. If on the other hand, it looks for configs in > /etc/opt..... you share out /opt/csw... and then it breaks, until > you go and have to copy in something to /etc/opt/csw on to **Every > Single Machine*** you want to run it on. > Not very large-scale-install friendly. Large-scale sites are exactly the same types of installations that would be using cfengine/puppet/etc to manage things like this. Do you agree that having two etc directories for an installation without nfs/zone sharing is pointless? Do you agree that if everything were in /etc/opt/csw and a site wanted to share their csw install, a move on the server of /etc/opt/csw to /opt/csw/etc and a symlink of /etc/opt/csw -> /opt/csw/etc on the all machines consuming this particular /opt/csw would handle things just fine? (Packages wanting/needing local customization could still symlink individual files to somewhere else as you noted.) I realize that Rupert raised concerns about this, due to restrictions in his environment, so it might be nice to get his thoughts (or the thoughts of others in a shared-csw setup) on this. I'm not in the position of having to deal with something like this. It would also be nice, but difficult to determine, how many sites actually use csw like this. 1%? 5%? More? Less? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu Contact me to arrange for a CAcert assurance meeting.
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
