On 11/28/12 08:34, Antoine Jacoutot wrote:
On Wed, Nov 28, 2012 at 08:28:10AM +0100, Alexander Hall wrote:
Make sure new config is valid before SIGHUP'ing sshd, which would
otherwise just kill it. Invalid configuration now gives:
# pgrep sshd
18998
# /etc/rc.d/sshd reload
sshd(failed)
#
I like this - it's what -t is intended for.
On Wed, 28 Nov 2012, Alexander Hall wrote:
Make sure new config is valid before SIGHUP'ing sshd, which would
otherwise just kill it. Invalid configuration now gives:
# pgrep sshd
18998
# /etc/rc.d/sshd reload
sshd(failed)
# pgrep sshd
18998
Then running dhcpd with pf-support (-A tbl -C tbl).
dhcpd spawns child process which is not handled by rc-script then stop/restart.
Here is a diff to fix it.
Yes, I know, normally one might want to flush PF-tables as well and this is not
handled by the diff.
But at least I don't have to kill
On Wed, Nov 28, 2012 at 08:28:10AM +0100, Alexander Hall wrote:
Make sure new config is valid before SIGHUP'ing sshd, which would
otherwise just kill it. Invalid configuration now gives:
# pgrep sshd
18998
# /etc/rc.d/sshd reload
sshd(failed)
# pgrep sshd
18998
Pros: Less risk of
On 23/11/12(Fri) 11:40, Martin Pieuchot wrote:
Diff below adds support for Uninorth AGP bridges found in most if not
all the macppc machines with a G3 or G4 microprocessor.
These chips do not translate individual pages using the GART like it
is the case for most of the AGP chips on
2012/11/27 Mike Belopuhov m...@belopuhov.com:
apply the diff and see how all your apps are happily using single
device node: /dev/bpf0.
i'm not 100% sure we want this but why wouldn't we?
generally speaking we also need to move to a single /dev/bpf
node, but that can be done, once this diff
mxb m...@alumni.chalmers.se wrote:
Then running dhcpd with pf-support (-A tbl -C tbl).
dhcpd spawns child process which is not handled by rc-script then
stop/restart.
Here is a diff to fix it.
Yes, I know, normally one might want to flush PF-tables as well and
this is not handled by the diff.
On 2012/11/28 10:24, mxb wrote:
Then running dhcpd with pf-support (-A tbl -C tbl).
dhcpd spawns child process which is not handled by rc-script then
stop/restart.
This is a bug in dhcpd, not the rc script.
Compiling if_ix.c with IX_DEBUG yields
../../../../dev/pci/if_ix.c: In function 'ixgbe_print_hw_stats':
../../../../dev/pci/if_ix.c:3525: error: 'struct ix_softc' has no member named
'mbuf_alloc_failed'
../../../../dev/pci/if_ix.c:3526: error: 'struct ix_softc' has no member named
On Tue, Nov 27, 2012 at 10:17 PM, Mike Belopuhov m...@belopuhov.com wrote:
apparently it works just fine. the number of clones is limited
by the v_specbitmap which currently allows for 64 clones total
(per system, not per process).
Please clarify: Does it mean 64 cloned bpf devices per
On Wed, Nov 28, 2012 at 12:43 PM, Reyk Floeter r...@openbsd.org wrote:
On Tue, Nov 27, 2012 at 10:17 PM, Mike Belopuhov m...@belopuhov.com wrote:
apparently it works just fine. the number of clones is limited
by the v_specbitmap which currently allows for 64 clones total
(per system, not per
Alexander Hall alexan...@beard.se wrote:
IIRC, isn't there a few distinct (non-ifconfig-compatible) cases we
handle specially, and the rest is passed as-is to ifconfig?
Is it?
Okay, I've looked at the netstart code again. It messes with any
lines where
* the first word is dhcp, rtsol, inet,
Date: Tue, 27 Nov 2012 15:02:31 +0100
From: Martin Pieuchot mpieuc...@nolizard.org
While working on drm support for macppc that makes use of non-cached
memory I found that some platforms (amd64, i386, powerpc) use the MD
PMAP_NOCACHE flag where others (sparc, sparc64, solbourne) use PMAP_NC
Hi,
inspired by mikeb@'s clonable bpf patch, this slightly more complex
diff implements clonable interface support to tun(4).
The idea is to split the fixed relation between device minor number
(/dev/tunX) and interface unit (ifconfig tunY). In difference to the
current tun(4) implementation,
Date: Wed, 28 Nov 2012 17:39:24 +0100
From: Reyk Floeter r...@openbsd.org
Hi,
inspired by mikeb@'s clonable bpf patch, this slightly more complex
diff implements clonable interface support to tun(4).
The idea is to split the fixed relation between device minor number
(/dev/tunX) and
From: Mike Belopuhov m...@belopuhov.com
Date: Wed, 28 Nov 2012 22:21:07 +0100
On Wed, Nov 28, 2012 at 8:21 PM, Mark Kettenis mark.kette...@xs4all.nl
wrote:
Date: Wed, 28 Nov 2012 17:39:24 +0100
From: Reyk Floeter r...@openbsd.org
Hi,
inspired by mikeb@'s clonable bpf patch, this
On Wed, Nov 28, 2012 at 1:42 PM, Mark Kettenis mark.kette...@xs4all.nl wrote:
But currently /dev/tunN is usable from any programming language that
that can do reads and writes. With Reyk's changes you need to do an
ioctl even for basic usage, which is at best quirky in languages other
than
there's not supposed to be bpf0,1,2,3...
Unfortunately history argues otherwise.
On Wed, Nov 28, 2012 at 11:38 PM, Theo de Raadt dera...@cvs.openbsd.org wrote:
there's not supposed to be bpf0,1,2,3...
Unfortunately history argues otherwise.
no, i meant if we move to the clonable bpf, we will need only one node.
sorry for not making it clear.
On Wed, Nov 28, 2012 at 10:42 PM, Mark Kettenis mark.kette...@xs4all.nl wrote:
But currently /dev/tunN is usable from any programming language that
that can do reads and writes. With Reyk's changes you need to do an
ioctl even for basic usage, which is at best quirky in languages other
than
Hi,
because of a bug in ospf6d I tried to allow ospf6d to change cloning
routes to gateway routes and the other way around. I've noticed there is
a check which tries to forbid this, but the check is broken. It allows to
toggle ALL rt flags, if ONE common bit in RTF_FMASK and rtm_fmask is set.
21 matches
Mail list logo
