search for: booom

...t. i do have sufficent power supply and raspi is running headless with no additional peripherals. without tinc installed, it runs flawlessly 24/7 via wlan or eth0 or even both. with tinc installed, it runs flawlessly 24/7 via eth0 with tinc still installed, power off, plug in wlan, power on -> booom. so there maybe a serious conflict with other software (network, wpa-gui,..?). sven

...server. I have done almost everything, so the new server has the data, the ACLs are transfered and are ok, but when I shut down the old server, change the hostname of the new one to old one, changed the SID of the new server to the old server (using net getlocalsid/net setlocalsid xxx) and... booom. When I try to access the shares on the new server (from windows) it asks for user name/password just like the new server is not a member of the domain. So is it possible to achieve what I want? I'm not sure if other way, by using net ads leave (on new server) and then join with changed n...

tinc 1.0.19 worked fine on Raspberry Pi as long as my Pi was connected via ethernet cable. Today i changed the connection to wlan. Pi crashed. worse, it was no longer operational, even if connected via cable. recovery from backup before tinc was installed (yes, i had a backup ;) tried again. installed tinc: worked as long as connected via cable. crash after connecting via wlan. no longer

http://dovecot.org/test/ Just mbox fixes since 1.0-test16. The logic is simpler and more correct now. Can anyone break it anymore? I actually tested it a while with Evolution and several mailboxes and it didn't break at least immediately. :) Now maybe a few more days and I dare trying this thing myself with my real mboxes (yes, I'm still using them). Dovecot mailing list archives could

Hi, I try to build experimental networks with Xen and stumbled over the same problem that has been described quite well by Mark Doll in his posting "xen_net: Failed to connect all virtual interfaces: err=-100" here: http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS and NR_DYNIRQS had been

Hi, I try to build experimental networks with Xen and stumbled over the same problem that has been described quite well by Mark Doll in his posting "xen_net: Failed to connect all virtual interfaces: err=-100" here: http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS and NR_DYNIRQS had been

SUMMARY: -------- I tried to identify the general and root causes for these problems with 1.9, by taking into account non-utf encoding, current patches, comments and ideas. I used ticket #2188 as base for explanations. This is a long read. I wanted to include all the relevant information in one place. I also included information about related tickets in LH and their status. I decided that adding