Hello
I need the advise. Does anybody got the Subj working?
I have FreeBSD 7.3-p2, Generic kernel. I try to set up the netflow traffic
accounting using ng_ipfw from vlan interface. I created vlan interface, ipfw
rule, set up ng hooks but the netflow export is not working. tcpdump does
not catc
Hi.
Sorry for cross-posting, got nothing back from freebsd-ipfw...
Installed a new router running 8-stable and encounter some problems when
configuring dummynet pipes:
When setting buckets above 1024...
ipfw pipe 91 config bw 100Mbit/s mask src-ip 0x buckets 4096
...I get the following
Hi list,
I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured.
I've found out that only a few of them are terminated normally (via
/etc/rc.shutdown) during the system shutdown. FreeBSD reports that
20sec interval has elapsed and simply kills all the jails that are not yet
termi
on 20/09/2010 11:42 S.N.Grigoriev said the following:
>
> Hi list,
>
> I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured.
> I've found out that only a few of them are terminated normally (via
> /etc/rc.shutdown) during the system shutdown. FreeBSD reports that
> 20sec interv
> I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured.
> I've found out that only a few of them are terminated normally (via
> /etc/rc.shutdown) during the system shutdown. FreeBSD reports that
> 20sec interval has elapsed and simply kills all the jails that are not yet
> termin
20.09.10, 13:37, "Erik Stian Tefre" :
> > I use a server (FreeBSD 8.1R amd64) with two dozens of jails configured.
> > I've found out that only a few of them are terminated normally (via
> > /etc/rc.shutdown) during the system shutdown. FreeBSD reports that
> > 20sec interval has elapsed and
On 2010-Sep-18 08:32:32 -0500, Bryce Edwards wrote:
>I have a Supermicro with the C7X58 motherboard and an i7 930 cpu, and
>it is nowhere near the performance it should be. A buildworld just
>took 22.5 hours!
That does sound a bit poor. I presume the system was basically unloaded
during the bui
TB --- 2010-09-20 13:24:47 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-20 13:24:47 - starting RELENG_8_1 tinderbox run for amd64/amd64
TB --- 2010-09-20 13:24:47 - cleaning the object tree
TB --- 2010-09-20 13:25:45 - cvsupping the source tree
TB --- 2010-09-20 13:25:45 - /u
TB --- 2010-09-20 14:35:18 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-09-20 14:35:18 - starting RELENG_8_1 tinderbox run for ia64/ia64
TB --- 2010-09-20 14:35:18 - cleaning the object tree
TB --- 2010-09-20 14:36:08 - cvsupping the source tree
TB --- 2010-09-20 14:36:08 - /usr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 9/19/2010 11:55 AM, Mark Kamichoff wrote:
| Well, you can safely ignore this! I realized afterwards that
| '--disable-ipv6' just disables the default use of IPv6 in BIND, it
| doesn't completely disable the protocol. Turns out I was querying th
10 matches
Mail list logo