Physically disconnected the exterior lan cable, did a vos changeaddress to
10.1.1.194 then had to manually vos remsite 4 each sites per volume with
address 10.1.1.194 for each volume, did a vos release and all is working
without external lan.
Looks like the multiple replication sites on each
Hello, all.
We (hcoop.net) currently have Courier working using Maildirs stored in
afs (OpenAFS client, OpenAFS server). It's working quite well, except
for the fact that courier's authentication mechanism is extremely
kludgey and required a good bit of hacking in order to make it utilize
Cyrus was designed to use a local filesystem with Unix semantics
and a working mmap()/write() combination. AFS doesn't provide
these semantics so won't work correctly.
http://www.ibr.cs.tu-bs.de/cgi-bin/dwww?type=filelocation=/usr/
share/doc/cyrus21-doc/html/faq.html
Is this still the
Whether or not cyrus works with afs now, it does not seem to be a good fit
for your scenario. cyrus is a black box mail system. All the mail files
are owned by the cyrus user and live in filesystem trees designated as
cyrus partitions. The daemons all run as the cyrus user and PAM
On Thu, 26 Apr 2007 [EMAIL PROTECTED] wrote:
On Tue, 24 Apr 2007 [EMAIL PROTECTED] wrote:
We are serving up a virus .dat file to mail relays via AFS
readonly. The file is periodically updated, the volume where it
lives is re-released hourly whether update occured or not. Read
On Sun, 20 May 2007, ted creedon wrote:
Unless I've missed something, afs now listens to any interface that is up,
internal and external.
now, as in this epoch?
I thought that afs listened only to the interface that carried the host
address and additional addresses could be added via the
