On Nov 30, 2004, at 11:49 AM, Rainer Duffner wrote:
John Berliner wrote:
In the kernel, is UFS_DIRHASH enabled, or whatever the option is? This caused a lot of trouble on another server i admin, where it would be so slow, that at times login sporadically failed. It is enabled by default, and it would be stupid to have been removed, but you never know.Hm...I'm pretty new to BSD (more used to Linux) so I'm not sure how to discover kernel compile options...but AFAIK the guy who set all this stuff up just used a generic 4.6 kernel config.
The FreeBSD handbook and FAQ (directly linked from http://www.freebsd.org) makes an excellent reading and goes to great lengths explaining the details, which in the end boils down to editing one file and executing a handful of commands (in the right sequence.
The UFS_DIRHASH options is - TTBOMK - only useful when creating new filesystems.
It doesn't have any effect later-on. Well, shouldn't. ;-)
UFS_DIRHASH was introduced with or post-RELENG_4_6, IIRC, together with making softupdates the default at installtime....
Did not know this. Stepped into freeBSD from Linux in RELENG_4_6_2, and then did a reinstall for RELENG_4_7.
If anything see if it is possible to at least upgrade to the last 4.10 version, as there have been a lot of overall improvements (This is off topic BTW)Yeah, that's on my overly long to-do list.
It should be on top. ;-)
4.6 contains numerous vulnerabilites and is no longer supported. Looking at it, it was released in June 2002 - that's a long time in FreeBSD-land.
If you have a test-machine, you can try going from 4.6 to 4.10 directly via cvsup.
Otherwhise, I'm not 100%sure if going straight from 4.6 to 4.10 works (it should, but the devil is a squirrel, as we say here around) - read /usr/src/UPDATING for more information.
I suggest a clean reinstall, if you pick RELENG_4_10, it will be a clean start, as there are a ton of old libraries that are in RELENG_4_6.
Personally i suggest RELENG_5_3 though, has given me a more stable system, that is far more responsive, but i guess it is personal choice.
Also, when you manually auth using pop3:
telnet localhost 110 user <username> pass <password> list
What is the output? (Please truncate, if the user has a ton of emails, we don't need the entire list)
Or does it die saying can't scan maildir?per my earlier post, it dies with the Maildir scan ERR.
Does this only happen for his account,yes
and have you tried to mv the Maildir,and then /var/qmail/bin/maildirmake Maildir in the same dir, then chowning it to the right user and then trying to login again to see if it succeeds then?I didn't try that, but when I do, it authenticates correctly. This is good.
So now: I read somewhere that it's not a great idea to manipulate the queues directly; what's the consensus? Can I not just move the messages back into the appropriate directories in the new Maildir I just created?
The "queue" is in /var/qmail/queue and it *is* a bad idea to manipulate it directly (unless You Know What You Are Doing (TM).
But what you're manipulating here is the maildir. If you shut down qmail while you move the mail to the old place, you are 100% safe.
As it crashes with POP, the error should be in the top-level maildirectory somewhere, I assume.
If you're bored, you can truss -p the process after you connected with telnet and before you authenticated ;-)
I did that when i had the same problem, and did not find anything.
It seems to happen when some message is screwed up in some way. But this user i was tryingt it out on had over 60,000 emails, so finding the culprit woulda been painfull.
If you have further ambitions with your Qmail-installation, you might want to check-out Matt Simerson's Qmail-FreeBSD-Toaster at http://www.tnpi.biz.
Though it's geared towards ISPs, it does also work very nicely for smaller installations.
Shameless plug <url:http://bsdguides.org/guides/freebsd/mailserver/ qmail+vpopmail+qmailadmin.php>. Guide was written by me, site owned by a friend of mine. It is geared to using the FreeBSD ports tree to make install easier. And includes all the standard stuff you would want (imap, pop3, sa, qmailadmin, qmail, vpopmail)
Good luck with your install.