To make this problem even stranger, I can make a connection from the
server to a workstation without issue. It appears to only be incoming
We've seen something very similar to this; we assumed it was
EEPROM corruption.
Is this a Dell PowerEdge by chance?
Do you have TSO enabled?
On 9/30/2010 4:11 AM, Kaya Saman wrote:
I mean for a DNS server (all be it a small one) is it wise to use
compact flash as storage??
For our GSLB DNS Slaves, we boot embedded/low power (or even VMs these
days) systems with CF images off of flash, keep a shadow copy of /etc
around, and
All:
It's a bit hard to track where we stand with this issue. Is
anyone having success running client-bridge (wifi0 in client
mode, briding to wired interfaces)?
From assorted posts, I understand ath(4) can't transmit from
arbitrary source MACs or there's some limitation to the the
All:
DHCP:
option root-path 192.168.224.67:/export/tftpboot/root-db;
loader.rc:
set vfs.root.mountfrom=nfs
set vfs.root.mountfrom.options=rw
set boot.nfsroot.path=/export/tftpboot/root-web
set boot.nfsroot.server=192.168.224.67
loader.conf:
mfsroot_load=NO
nfsclient_load=YES
On 4/26/2010 9:05 AM, Efren Bravo wrote:
I've OpenSSL 1.0.0 installed and ports up2date.
My server is on production, so, What do you think I should do in my case?
Okay yea you'll need 5.0.1 and a copy of KR or Stevens` APUE to help
hold you down. [1]
~BAS
1. Down under water, until the
All:
The install.cfg mechanism is pretty wicked.
Unfortunately, there doesn't seem to be a really efficient way
to provide new clients (or class of clients) an install.cfg
without rebuilding an MFSROOT image.
At least with pxeboot(8), in TFTP-only-mode, using
dhcpd.conf(5) client{}
All:
I've got a process that is mysteriously receiving a SIGTERM (or other
signal. It's a RADIUS daemon; runs a non-Root (not privsep,
unfortunately). Identical hardware, identical code, identical
config on 6.3-PL is fine.
On 8, the daemon is logging receipt of a non-HUP signal and
On 1/25/2010 12:15 PM, Peter Ankerstål wrote:
How do I set a static ipv6 route in rc.conf?
This command works: route add -inet6 -net 2003:16c8:dc1e:2:: -prefixlen 64
2003:16c8:dc1e::2
and I use this in rc.conf:
ipv6_static_routes=2003:16c8:dc1e:2:: -prefixlen 64 2003:16c8:dc1e::2
Do it
http://m.de.yahoo.com was running YTS on Linux when last queried at
19-Dec-2009 19:12:25 GMT - refresh now Site Report
Hard to stand, I'd expect FreeBSD get replaced by Windows because of
MS/Yahoo! agreement, but Linux??
Its possible the frontend loadbalancer/L4 switch is an A10 at Yahoo!,
Anthony M. Rasat wrote:
Dear all,
I have two (ethernet) network interface with IP address within the same subnet, call it msk0 and nfe0.
Interface msk0 have IP address 192.168.0.2 and nfe0 192.168.0.3 and default router IP address is 192.168.0.1.
route(8) takes a 'dev' argument, but the
As far as I can tell, it doesn't even get to the certificate
verification phase even though the STARTTLS command is successful.
Is there any level of debugging that can be increased on the Apache side
? Possibly a build/compile-time option for the module?
Debugging apache code can always
I really think that it should be corrected to:
cd /usr/src
make distribution DESTDIR=$D
That's almost certainly correct, but it notes:
Notes
[1] This step is not required on FreeBSD 6.0 and later.
But then I get this error in syslog:
bind: Can't assign requested address
That's a
12 matches
Mail list logo
