* PC:
If you're just fighting IOPS, another compromise might be using a ramdisk,
and then committing that data to storage every x seconds.
In this case, it's more straightforward to remove the fsync call from
dhcpd.
--
Florian Weimerfwei...@bfk.de
BFK edv-consulting GmbH
* Jimmy Hess:
On Wed, Jul 20, 2011 at 9:31 AM, Nick Colton ncol...@allophone.net wrote:
We were seeing similar issues with low leases, moved the dhcpd.leases file
to a ramdisk and went from ~200 leases per second to something like 8,000
leases per second.
Yes, blame RFC2131's requirement
Marginally operational, but I'm sure there are at least a few folks using
that service as part of monitoring, so it probably bears mentioning.
ATT appears to be having an email-to-SMS gateway issue. Messages sent to
xxx...@txt.att.net are not being delivered to handsets. No bounce, but
no
Just wanted to drop a note as a was pretty harsh on Apple when rumors
of them not including DHCPv6 client support were floating about. In
the past few days I've also seen people post that OS X doesn't have
DHCPv6, because they were looking for DHCPv6 in the UI. Thankfully
these reports are
In a message written on Mon, Jul 25, 2011 at 10:50:21AM -0400, Ray Soucy wrote:
Just wanted to drop a note as a was pretty harsh on Apple when rumors
of them not including DHCPv6 client support were floating about. In
the past few days I've also seen people post that OS X doesn't have
DHCPv6,
On 25 Jul 2011, at 15:50, Ray Soucy wrote:
Just wanted to drop a note as a was pretty harsh on Apple when rumors
of them not including DHCPv6 client support were floating about. In
the past few days I've also seen people post that OS X doesn't have
DHCPv6, because they were looking for
Hello,
I work for a French operator, so I know well
wholesales solutions E1/Sdsl/Adsl online a few countries
Europe.
I am looking to find how wholesales work in the U.S.,
basically, we would be in New York City and would have
a wholesales Dsl/T1 issued or L2TP VLAN. I tried
contact operators
This appears to have just been restored.
--
Adam Kennedy
Network Engineer
Omnicity, Inc.
From: Drew Linsalata drew.linsal...@gmail.commailto:drew.linsal...@gmail.com
Date: Mon, 25 Jul 2011 08:00:25 -0400
To: NANOG nanog@nanog.orgmailto:nanog@nanog.org
Subject: ATT Email/SMS gateway outage
I don't think what you are after will be as feasible as it sounds like
you're used to in Europe.
In the US, there are _many_ different telephone companies each servicing a
certain area, and they each have different policies and procedures on
whether they will offer wholesale DSL in a given
Hello All:
We will be moving the mailing list at 12:00 PDT (GMT -7). The following is the
cutover schedule and expected issues during the cutover.
1) 12:00 - move DNS for mailman.nanog.org (the MX for nanog.org)
2) 12:00 - shut down Mailman on s0.nanog.org (mailman.nanog.org)
3) 12:01 - final
This message is testing the new list server configuration. Please ignore.
Mike
--
Michael K. Smith - CISSP, GSEC, GISP
Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com
w: +1 (206) 404-9500 f: +1 (206) 404-9050
PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D)
We are holding on this conversion at the moment and running on the existing
configuration. I will update the list shortly with a revised schedule.
Regards,
Mike
--
Michael K. Smith - CISSP, GSEC, GISP
Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com
w: +1 (206) 404-9500 f: +1
Hello:
We have moved the NANOG mailing list to its new location. I've sent and
received a test message successfully. If anyone is having issue after they
have confirmed they have the correct DNS settings, please send me an email
directly.
204.93.212.138
And
Hello Everyone:
The correct and updated IPv6 address for the NANOG list is
2001:1838::cc5d:d48a. Forward and reverse records are updated and the
other address will continue to work while the DNS change propagates.
Regards,
Mike
14 matches
Mail list logo
