MEI Technology Consulting, Inc
[EMAIL PROTECTED]
(516) 379-0001 Office
(516) 480-1870 Mobile/Emergencies
(516) 908-4185 Fax
http://www.meitech.com/
-Original Message-
From: Thomas Foster [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 4:48 AM
To: Gustafson, Tim
Cc: [EMAIL
PROTECTED]
(516) 379-0001 Office
(516) 480-1870 Mobile/Emergencies
(516) 908-4185 Fax
http://www.meitech.com/
-Original Message-
From: Thomas Foster [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 02, 2005 7:57 AM
To: Gustafson, Tim
Cc: [EMAIL PROTECTED]
Subject: Re: Routing Problem
Hi Tim
I am having a problem setting up a multi-homed host. I have two
separate T1 internet connections, and one physical NIC in my FreeBSD
box. The two networks are as follows:
Connection 1:
LAN Address: 1.2.3.24/25
Router Address: 1.2.3.1
Connection 2:
LAN Address: 4.5.6.106/29
Router Address:
Hello!
Is there any way to turn on threaded Perl in the base system, instead of
using the Perl port? I need to use p5-Sendmail-Milter which requires
threads, but I would rather not install the Perl port over the base Perl
installation. Is there any flag I can set in /etc/make.conf that will
Sergey,
I have submitted the problem to FreeBSD using the send-pr program, as
Jonathan Chen asked me to. I will follow up here with some details for you
though.
Once the problem starts happening, it seems that I have to log off the
system and log back in again to fix it. This usually (95% of
Hello everyone.
I finally have the output of a ktrace of the problem where vi returns
Error: input: Resource temporarily unavailable to me. It can be
downloaded from the following link. Any information that can tell me what's
going on here and maybe what I can do to fix it would be greatly
I am getting the following error in vi pretty consistently:
Error: input: Resource temporarily unavailable
Usually I get this at every attempt I make to run vi. Every now and then
I'll somehow manage to stay in vi however long I want. It seems that if
it's going to bomb, it bombs in the first
Hello
I have a brand spanking new Supermicro 7043P-8R server with dual Intel
3.2gHZ Xeon processors and 4GB of Kingston memory.
I installed FreeBSD 4.9 on the box and it gives me the following message on
the screen about 2-5 minutes after it finished booting:
boot() called on CPU#0
I get this
