On Tuesday 07 October 2014 11.56:04 Philipp Storz wrote: > Am 07.10.2014 11:43, schrieb Bruno Friedmann: > > > > > > ok thanks will try that tonight even if administrator right start to means > > nothing under 8,1 :-) > > > > Ok, very nice, so you can tell me how it works on 8.1. > > Until now, I have only debugged on xp, windows 7, 2008, 2012. I hope it is > possible on 8.1 also :) > > Does this problem only happen on 8.1 or also on win 7? If it does, on > windows7 it is definitely > possible to debug. > > > Best regards, > > Philipp > > > It happen also on win2012 server, I've forced the linux/bareos to only use ipv4 to not crash the bareos-fd ... so I guess it also possible to reproduce on any win plateform.
And I suspect it could also be the case with linux when you try to let the bsock.c listen on the two protocol with just using FDPort (or any other daemon). But I need to dig more in test and draft them completely to be useful. Before this incident, I've used the way to choose only one of the protocols ipv4 OR ipv6 and enforce it on any device. Now time is to debug ... -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
