Re: NSD 3.2.15

2013-02-06 Thread Brad Smith
On Wed, Feb 06, 2013 at 04:31:05PM +, Stuart Henderson wrote: > Here is an update to NSD, the most notable new thing is the code > for response rate limiting support (similar to the ratelimit flavour > of ports/net/isc-bind but an independent implementation), however > this is not yet enabled b

Re: Workaround for an rsu(4) bug

2013-02-06 Thread Brad Smith
On Tue, Feb 05, 2013 at 12:26:47AM +0100, Mark Kettenis wrote: > > Date: Tue, 29 Jan 2013 21:04:30 -0500 > > From: Brad Smith > > > > To a certain extent this seems to make rsu(3) work a little better, but > > now I am seeing ``rsu0: could not send join command'' messages which never > > happened

Re: Xorg triggers panic w/ Intel HD4000 graphics

2013-02-06 Thread RD Thrush
On 02/06/13 09:52, Mark Kettenis wrote: >> Date: Wed, 06 Feb 2013 06:39:48 -0500 >> From: RD Thrush >> >> Using startx as root w/ no Xorg.conf causes -current to panic when >> using the i7-3770 integrated graphics adapter. I built a debug >> kernel and sent a sendbug report[1] on Sunday. I've ap

Re: Xorg triggers panic w/ Intel HD4000 graphics

2013-02-06 Thread Mark Kettenis
> Date: Wed, 06 Feb 2013 06:39:48 -0500 > From: RD Thrush > > Using startx as root w/ no Xorg.conf causes -current to panic when > using the i7-3770 integrated graphics adapter. I built a debug > kernel and sent a sendbug report[1] on Sunday. I've appended a > (serial console) excerpt from that

Xorg triggers panic w/ Intel HD4000 graphics

2013-02-06 Thread RD Thrush
Using startx as root w/ no Xorg.conf causes -current to panic when using the i7-3770 integrated graphics adapter. I built a debug kernel and sent a sendbug report[1] on Sunday. I've appended a (serial console) excerpt from that report. The panic is easily reproducible. Is this a known proble

Re: Send hostname to remote host with syslogd

2013-02-06 Thread Gabriel Linder
On 02/01/13 15:30, Gabriel Linder wrote: > On 02/01/13 11:57, Stuart Henderson wrote: >> I'm a bit undecided as to whether this is really useful (I suppose >> having it _in addition_ to the IP address might be useful where >> there's a NAT between log source and destination) but in any event >> if