I was looking at trying out flow monitoring and I found pfflowd, but
unfortunately it does not work with FreeBSD 9.0. I thought about ng_netflow
but that doesn't see my tun interface which may be related to..
WARNING: attempt to domain_add(netgraph) after domainfinalize()
Noise message. I've
Matthew,
Although netwait will probably fix the problem for you, another
possibility that I have just ran into recently involved DNSSEC
validation in bind. The problem was that without ntp syncing the time at
boot (the system doesn't have battery backed time) dns resolution failed
(root
- CPU_SOEKRIS, CPU_GEODE, CPU_ELAN, NO_SWAPPING for embedded devices
Embedded devices are out of the scope of this, normally you do a lot of
other modifictions to such systems anyway, so a custom kernel should be
not a big problem.
Just as a quick data point here, I have just installed FreeBSD
It depends on the type of group. There are at least two types of group objects
that you can use in LDAP but only one of them works. You need to use posixGroup
objects for unix groups. As I remember it, these have memberUid attributes for
the member ids. These are simple unix identifiers.
(combined posixGroup/groupOfNames) for everything is extremely tempting.
Enjoy,
Brian
-Original Message-
From: owner-freebsd-sta...@freebsd.org
[mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Scott, Brian
Sent: Thursday, 25 February 2010 11:18 AM
To: Gerrit Kühn; freebsd-stable
In a word, 6tunnel. It's an application level proxy that does the job
well enough to get you out of trouble. Another approach would be to run
netcat (nc) from inetd on the port in question.
That said, I'll add my voice to the suggestion that it is very simple to
get IPv6 going on pretty much
Try:
wheel:*:0:root,us
It looks like pam was stopping at the first matching line as you would
expect from the man page for the group file. If there is a bug it is in
the more liberal interpretation by other software.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
suggesting
ways of finding out what file/line has the problem.
Good luck,
Brian
-Original Message-
From: olivier.taylor [mailto:[EMAIL PROTECTED]
Sent: Friday, 16 June 2006 3:47 PM
To: Scott, Brian
Cc: freebsd-stable@freebsd.org
Subject: Re: save-entropy
Thanks Scott,
But unfortunately
That would be the old 'accidentally deleted a # from a line in rc.conf'
problem. There are likely to be several lines beginning '# -- ' in the file.
New users often accidentally remove the # making the '--' into a command. There
will also be a few messages during startup that will also complain
For what its worth I use Norton Ghost to regularly set up a classroom of
machines with FreeBSD 5.3, mostly because other teachers put Windoze
stuff on the same boxes so the Ghost setup makes sense.
Ghost doesn't understand UFS but doesn't need to. It just takes a block
by block copy of the whole
10 matches
Mail list logo
