Strange problems bootstrapping 2.0.3

[Richard Bos]

Op zaterdag 29 april 2006 23:12, schreef Michael Leupold:
> I happened to find out what caused this. Some file-permissions were wrong
> (that's what kolabcheckperm said). It seems kolabconf hasn't been running
> successfully at all. After changing permissions manually, everything seems
> to work just fine. Unfortunately I didn't write down what kolabcheckperm
> gave me on its first run, but the most important part for me might have
> been: File /kolab/etc/imapd/imapd.conf has the wrong persmissions/owner.
> Found 644 kolab:kolab, expected 640 kolab:kolab-r
> Please note that this is verbatim and the typo wasn't mine :)
>
> The version I'm using now is 2.1-beta1 which still showed the above
> behaviour. Still no apache.local...

Change log level in /kolab/etc/kolab/kolab.globals.  Make it e.g. 4
tail //var/log/messages, after that run 'kolabconf -n'

-- 
Richard Bos
Without a home the journey is endless