Date: Sat, 5 Aug 1995 02:55:27 -0700 (PDT) From: Robert Du Gaue <rdugaue@calweb.com> To: questions@freebsd.org Subject: qpopper problems Message-ID: <Pine.BSF.3.91.950805024657.7866A-100000@web1.calweb.com>
next in thread | raw e-mail | index | archive | help
I run a small (but rapidly expanding!) ISP using FreeBSD and pent90s/100s (one SGI). Lately I've had terrible problems with the BSD machines spontaneously resetting. I've tracked this down to what I believe is a serious problem with popper. I have my users connect to 'pop.calweb.com' for their pop host, and wherever that resolves to that machine becomes unstable. I have 3 users machines, and one evening I was basically able to get each machine to reset by switching pop resolution to each. Tonight, although pop resolved to a different machine, one of the others crashed 3 times. Sure enough going into the log files shows someone doing pop requests using the machines name (not the pop alias) for the connection! I've commented out the pop3 config in inetd.conf for now, but I'm still gauranteed that the pop.calweb.com machine will be unstable. Has anyone else seen this? Two of the machines are on the OS just before this last snapshot (until I can upgrade gracefully it's tough to keep up! hint hint), and one of them is on 2.0.5. They all exhibit unstability with qpopper resolving to it. Should I also be contacting Qualcom? I'm wondering if it's actually their problem or something wrong with BSD... Any help would be greatly appreciated! As far as I can see these latest snaps have given my machines greater stability over the older versions (NFS is much better, but still gets whacked under heavy xfers) and if this qpopper problem could get resolved many of my current worries will be gone...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.950805024657.7866A-100000>