Programas Ejecutivos (INICIO Lunes 30 Agosto) ESEADE / NAYC

Cursos Intensivos en San Juan Diseqo y Documentacisn de Obras con REVIT de Autodesk 9 y 10 de Septiembre. de 9:00 hs. a 18:00 hs. Colegio de Arquitectos de San Juan General Acha entre Mariano Moreno y Belgrano Ges

Re: misc. ctl parser.c cleanup

hi ted, the diff is ok by me gilles On Sun, Aug 22, 2010 at 05:56:32PM -0400, Ted Unangst wrote: > I think this is slightly better, though there isn't much functional > change. This code certainly gets around... > > Index: dvmrpctl/parser.c > ==

Re: libevent signal whoopsie

On Thu, Aug 26, 2010 at 09:07:08PM +0100, Nicholas Marriott wrote: > hi > > libevent has this clever stuff to reinitialise signals if the backend > requires it after calling event_reinit() (typically called after > fork()). > > unfortunately, it isn't enabled for poll and select, so both parent a

libraries updates in recent X snapshots - please test.

Hi, recent X snapshots (dated aug 25 or later) contain a number of un-committed updates to various X libs, that need some wide testing. So, if you track -current, please update X as well as your base system from snapshots and give it a try. Updates include: - libfreetype 2.4.2 (with the byte

kernel build failed without IPSEC

kernel build failed, if IPSEC is *not* defined: ../../../../netinet/in_proto.c:214: error: 'etherip_input' undeclared here (not in a function) ../../../../netinet/in_proto.c:216: error: 'etherip_sysctl' undeclared here (not in a function) got OK from claudio@ need one more. OK? Index: in_prot

libevent signal whoopsie

hi libevent has this clever stuff to reinitialise signals if the backend requires it after calling event_reinit() (typically called after fork()). unfortunately, it isn't enabled for poll and select, so both parent and child continue to use the same socketpair for signals. one byte is written in

Re: bgpd config to announce one netblock only to one upstream

Claudio Jeker [cje...@diehard.n-r-g.com] wrote: > > Are you sure that problem still exists in 4.8 or -current? Because the way > networks are handled changed completely. There is no longer a special > static/connected global rule. Now explicit rules have a higher precedence > then the dynamic "net

Re: bgpd config to announce one netblock only to one upstream

On Thu, Aug 26, 2010 at 11:58:25AM -0700, Chris Cappuccio wrote: > Rod Whitworth [glis...@witworx.com] wrote: > > I'm looking after a bgpd setup which announces an IPv6 /32 and an IPv4 > > /21. > > > > Due to a need for some heavy traffic clients to have their traffic > > arrive via just one trans

Re: bgpd config to announce one netblock only to one upstream

Rod Whitworth [glis...@witworx.com] wrote: > I'm looking after a bgpd setup which announces an IPv6 /32 and an IPv4 > /21. > > Due to a need for some heavy traffic clients to have their traffic > arrive via just one transit I'd like to turn that /21 into a /22 and > two /23s and only advertise one

Re: misc. ctl parser.c cleanup

On Sun, Aug 22, 2010 at 05:56:32PM -0400, Ted Unangst wrote: > I think this is slightly better, though there isn't much functional > change. This code certainly gets around... > Fine with me. > Index: dvmrpctl/parser.c > === > RCS

Re: multiple specified interfaces for rarpd

On Thu, Aug 26, 2010 at 02:26:02PM +0200, Claudio Jeker wrote: > On Thu, Aug 26, 2010 at 08:51:50PM +1000, Jonathan Gray wrote: > > On Thu, Aug 26, 2010 at 12:34:19AM +1000, Jonathan Gray wrote: > > > Currently rarpd can only listen on all or one interface, the > > > following lets multiple interfa

Re: make carp(4) work on IPv6 only setups

On 2010/08/26 15:25, Claudio Jeker wrote: > On Wed, Aug 25, 2010 at 12:29:00AM +0100, Stuart Henderson wrote: > > On 2010/08/24 23:14, Claudio Jeker wrote: > > > carp(4) is normaly using IPv4 multicast for its announcements. In case > > > there are no IPv4 addrs set IPv6 multicast will be used. But

Re: make carp(4) work on IPv6 only setups

On Wed, Aug 25, 2010 at 12:29:00AM +0100, Stuart Henderson wrote: > On 2010/08/24 23:14, Claudio Jeker wrote: > > carp(4) is normaly using IPv4 multicast for its announcements. In case > > there are no IPv4 addrs set IPv6 multicast will be used. But since the > > code forgot to embed the oh so frea

Re: multiple specified interfaces for rarpd

On Thu, Aug 26, 2010 at 08:51:50PM +1000, Jonathan Gray wrote: > On Thu, Aug 26, 2010 at 12:34:19AM +1000, Jonathan Gray wrote: > > Currently rarpd can only listen on all or one interface, the > > following lets multiple interfaces be specified like dhcpd. > > previous diff missed usage as pointed

Re: multiple specified interfaces for rarpd

On Thu, Aug 26, 2010 at 08:51:50PM +1000, Jonathan Gray wrote: > On Thu, Aug 26, 2010 at 12:34:19AM +1000, Jonathan Gray wrote: > > Currently rarpd can only listen on all or one interface, the > > following lets multiple interfaces be specified like dhcpd. > > previous diff missed usage as pointed

Re: multiple specified interfaces for rarpd

On Thu, Aug 26, 2010 at 12:34:19AM +1000, Jonathan Gray wrote: > Currently rarpd can only listen on all or one interface, the > following lets multiple interfaces be specified like dhcpd. previous diff missed usage as pointed out by sthen/jmc Index: rarpd.8 ===