Thanks for the responses everyone. I have some reading to do. ;)
Eric
Thanks for the responses everyone. I have some reading to do. ;)
Eric
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, 2004-01-29 at 14:55, Franz Georg Köhler wrote:
> This occasionally happens with new kernel releases.
I'd like to know why.
> Swap your configuration...
Again, I'd like to know *why* it happens rather than blindly changing
configs. What if I had 3 interfaces, what would happen then? I
w
On Thu, 2004-01-29 at 14:55, Franz Georg Köhler wrote:
> This occasionally happens with new kernel releases.
I'd like to know why.
> Swap your configuration...
Again, I'd like to know *why* it happens rather than blindly changing
configs. What if I had 3 interfaces, what would happen then? I
w
All,
I am having a weird problem and I don't know if it's my config or
something about the 2.6 kernel. In a machine with two integrated NICs
(Penguin Relion 125), the 2.6 kernel reverses the assignment order of
the physical interfaces to eth0 & eth1. Such that my
/etc/network/interfaces configs e
All,
I am having a weird problem and I don't know if it's my config or
something about the 2.6 kernel. In a machine with two integrated NICs
(Penguin Relion 125), the 2.6 kernel reverses the assignment order of
the physical interfaces to eth0 & eth1. Such that my
/etc/network/interfaces configs e
for some basic info.
Devices attached to these controllers appear as /dev/cciss/cXdXpX
c=controller #
d=logical drive #
p=partition #
Thus the first partition on the first logical drive on the built-in
controller is /dev/cciss/c0d0p1.
Cheers,
Eric
--
Eric Sproul
nTelos OSS Engineering
-
for some basic info.
Devices attached to these controllers appear as /dev/cciss/cXdXpX
c=controller #
d=logical drive #
p=partition #
Thus the first partition on the first logical drive on the built-in
controller is /dev/cciss/c0d0p1.
Cheers,
Eric
--
Eric Sproul
nTelos OSS Engineering
-
On Wed, 2003-10-08 at 08:43, Markus Oswald wrote:
> > THen, the backend, this will be two failover enabled boxes with postgres
> > and openldap. They will be quad xeon 6GB ram.
>
> Isn't a QUAD Xeon just plain overkill?
> I haven't tested a setup with OpenLDAP, but a Postfix/Courier/MySQL
> setup
Hi,
Does anyone know if the new Sendmail bug:
http://www.sendmail.org/8.12.10.html
affects 8.11.x? I have a few non-Debian boxes still running 8.11.7 (the
3/31 patch didn't bump the version number), and I haven't been able to
find any specific info.
Thanks,
Eric
--
To UNSUBSCRIBE, email to [
On Sat, 2003-09-06 at 22:34, Russell Coker wrote:
> On Sat, 6 Sep 2003 00:08, Eric Sproul wrote:
> > until the entire message has been received and processed, the receiving
> > MTA is not responsible for the message. In fact, I think this is
> > RFC-specified. Why then,
On Fri, 2003-09-05 at 11:19, Tinus Nijmeijers wrote:
> cyrus huh? in that case: is cyrus-popd a drop-in replacement for UW-pop
> (ipopd) on debian?
> I seem to remember it is not.
You are correct. Cyrus uses a completely different method for storing
mail, so you cannot just install its POP daemo
On Fri, 2003-09-05 at 10:18, Tinus Nijmeijers wrote:
> On Fri, 2003-09-05 at 16:08, Eric Sproul wrote:
>
> > Yes, I know we could set a larger minimum interval for POP, but the
> > political implications of generating tech support calls about "why can't
> > I PO
On Fri, 2003-09-05 at 01:14, Russell Coker wrote:
> I was under the impression that Sendmail also queues everything to disk. How
> does it's queue operate then?
While the message is coming in, Sendmail buffers the message to memory,
optionally piping the DATA portion to a socket (for milter scan
On Thu, 2003-09-04 at 01:43, Rudi Starcevic wrote:
> Hi,
>
> Sorry to bother you all with this repeat question.
> I've have searched around and seen plenty of opinions but I'd like to
> ask again and get the latest from this list.
>
> Sendmail or Qmail ? That is my question.
Rudi,
I work at an
15 matches
Mail list logo