> -----Original Message----- > From: Dallas Engelken [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 28, 2001 10:39 AM > To: Vazquez Javier; [EMAIL PROTECTED] > Subject: RE: maildircache: Cache create failure > > > > -----Original Message----- > > From: Vazquez Javier [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, November 28, 2001 9:32 AM > > To: '[EMAIL PROTECTED]' > > Subject: maildircache: Cache create failure > > > > > > hi there > > > > I couldn't find any list-archive, so I don't now if it's a stupid > > question. > > ;-) > > > > anyway, here comes the error-message: > > > > <snip> sqwebmail: maildircache: Cache create failure - unable to create > > [EMAIL PROTECTED]<snip> > > > > there actually is no directory named /var/run/sqwebmail ... > have I missed > > something? > > > > * --with-cachedir=dir, --with-cacheowner=userid - SqWebMail uses a > cache of currently active logins. SqWebMail runs for each and > every HTTP request, and after starting, it needs to locate the > account's maildir. Because hitting the authentication module can > be expensive (think MySQL/LDAP query for every HTTP request!) > SqWebMail caches the login information, in order to avoid having > your authentication server brought down to its knees. By default, > the directory /var/cache/sqwebmail or /var/run/sqwebmail will be > used, owned by the bin user. These options can be used to specify > a different location for the sqwebmail login cache directory. > You MUST add a periodic cron job to run the cleancache.pl script > in order to delete stale cache records from the cache directory. > make install will display the message containing the text of the > cron job. > > to fix: > # mkdir /var/run/sqwebmail > # chown bin.bin /var/run/sqwebmail > > at least that is what i had to do on my 5.0pre5. > > Dallas >
Would have been easier to just leave the --with-cache-dir off your configure, just like sam said the other day its an option 99% of people do not need. http://www.mail-archive.com/sqwebmail%40inter7.com/
