-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
https://www.five-ten-sg.com/util/openchange.bash That assumes a starting point of a fresh Centos 6 install taking all the defaults for a desktop install, with eth0 setup on a fixed ip address, and a fully qualified hostname that is used to derive the mail domain, realm, and other items. It uses the nightly repository from inverse.ca - is that appropriate? # ./openchange.bash phase1 'DOMAINCHANGEME' 'adminpasschangeme!' # -- generate and install ssl keys # ./openchange.bash phase2 The first argument to phase1 is the samba domain with its 14 character limit. The samba realm is derived from $(hostname). Sogo 2.2 - is openchange-ocsmanager still supported or necessary, or is that going away? SOGO vs memcached - the wiki implies we should connect over a unix domain socket, but in that case we need to make sure the sogo user has permissions to the socket. I switched that to a localhost tcp socket, but tcpdump does not show anyone connecting to it. Perhaps we need "SOGoMemcachedHost = localhost:11211;" to specify the port number? Is there any simple test scenario that will force sogo to use memcached? Centos vs debian - /etc/sysconfig/clock on debian uses underscores rather than spaces. Something does not properly quote the ZONE variable, since on Centos that might be "America/Los Angeles". -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlTZgKEACgkQL6j7milTFsGyuACeMNHMpkK4QvvlF9xN1ekf4paI WMIAoIXXADOMlUW2mBVL6wFmLJhJ7SjD =wqIc -----END PGP SIGNATURE----- -- users@sogo.nu https://inverse.ca/sogo/lists
