> Once I built and installed from the source RPM, when I start and stop
> the cyrus-omapd server, I get the following errors:
>
> Exporting cyrus-imapd databases: runuser: warning: cannot change
> directory to /dev/null: Not a directory
> Importing cyrus-imapd databases: runuser: warning: cannot ch
Once I built and installed from the source RPM, when I start and stop
the cyrus-omapd server, I get the following errors:
Exporting cyrus-imapd databases: runuser: warning: cannot change
directory to /dev/null: Not a directory
Importing cyrus-imapd databases: runuser: warning: cannot change
di
Am Mi, den 15.02.2006 schrieb Rob Tanner um 17:53:
> Alexander,
>
> One of my major reasons for building cyrus-imapd myself rather than with
> an RPM is that the FC4 distro RPM version logs as the mail facility, and
> I do not want both the MTA and cyrus-imapd logging to the same syslog
I too
Alexander,
One of my major reasons for building cyrus-imapd myself rather than
with an RPM is that the FC4 distro RPM version logs as the mail
facility, and I do not want both the MTA and cyrus-imapd logging to the
same syslog file. Building from unmodified source, messages are logged
using t
Am Mi, den 15.02.2006 schrieb Rob Tanner um 1:56:
> I am trying to build cyrus-imapd-2.2.12 on a 64 bit system running
> Fedora Core 4. Configure dies instantly with the following error:
>
> checking build system type... Invalid configuration
> `x86_64-unknown-linux-gnu': machine `x86_64-unkno
Hi,
I am trying to build cyrus-imapd-2.2.12 on a 64 bit system running
Fedora Core 4. Configure dies instantly with the following error:
checking build system type... Invalid configuration
`x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized
configure: error: /bin/sh ./config
