search for: bitlbee

Some precisions: we are not alone, some projects had similar problem: http://bugs.bitlbee.org/bitlbee/ticket/785 And the problem is really coming from NSS initialization. Discussion about the issue here : http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html There is a workaround to use NSS with fork but it is more setting a flag to share some resources (primarily sockets) but must...

On Fri, Mar 20, 2015 at 4:40 PM, Emilien Kia <kiae.dev at gmail.com> wrote: Some precisions: > > we are not alone, some projects had similar problem: > http://bugs.bitlbee.org/bitlbee/ticket/785 > And the problem is really coming from NSS initialization. Discussion about > the issue here : http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html > Wow! Congratulations on finding the source of the problem, I bet this wasn't easy! I'm glad to see tha...

2015-03-21 17:06 GMT+01:00 Melkor Lord <melkor.lord at gmail.com>: > > On Fri, Mar 20, 2015 at 4:40 PM, Emilien Kia <kiae.dev at gmail.com> wrote: > > Some precisions: >> >> we are not alone, some projects had similar problem: >> http://bugs.bitlbee.org/bitlbee/ticket/785 >> And the problem is really coming from NSS initialization. Discussion >> about the issue here : >> http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html >> > > Wow! Congratulations on finding the source of the problem, I bet this > wasn...

...7:06 GMT+01:00 Melkor Lord <melkor.lord at gmail.com>: >> >> >> On Fri, Mar 20, 2015 at 4:40 PM, Emilien Kia <kiae.dev at gmail.com> wrote: >> >>> Some precisions: >>> >>> we are not alone, some projects had similar problem: http://bugs.bitlbee.org/bitlbee/ticket/785 >>> And the problem is really coming from NSS initialization. Discussion about the issue here : http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html >> >> >> Wow! Congratulations on finding the source of the problem, I bet this wasn't easy!...

Hello all, With a really fast lookup, I think it is probably a problem of NSS initialization (key loading...) . As the problem occurs only when upsd is forked and as nss is initialized ( https://github.com/networkupstools/nut/blob/master/server/upsd.c#L1008)before upsd deamonify ( https://github.com/networkupstools/nut/blob/master/server/upsd.c#L1035), I suspect NSS to not be fork-safe. I will

On Mar 12, 2015, at 11:55 PM, Melkor Lord <melkor.lord at gmail.com> wrote: > > On Mon, Mar 2, 2015 at 2:39 AM, Charles Lepple <clepple at gmail.com> wrote: > > > I thought start-stop-daemon was involved because it closes stdin/stdout file > > descriptors after exec()'ing the daemon. I tried "--no-close" option to no > > avail. After that, I

...gmail.com>: > >> > >> > >> On Fri, Mar 20, 2015 at 4:40 PM, Emilien Kia <kiae.dev at gmail.com> > wrote: > >> > >>> Some precisions: > >>> > >>> we are not alone, some projects had similar problem: > http://bugs.bitlbee.org/bitlbee/ticket/785 > >>> And the problem is really coming from NSS initialization. Discussion > about the issue here : > http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html > >> > >> > >> Wow! Congratulations on finding the source of the problem...

...tcsh (default), sh, csh, bash, fish, zsh • Editors Edit, Pico, Nano, Vi, Vim Soft : screen, tmux, irssi, epic, bitchx, mc, links, lynx, wget, ekg, unrar, unzip, unarj, unace, weechat, psybnc, eggdrop, znc, git, cvs, sqlite3, rsync, curl, darcs, mercurial, bazaar, monotone, trac, fish, finch, bitlbee, django, pylons, zope, node.js, Catalyst If you want create account you need log on port 30 SSH host shellmix.com as newuser password newuser -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" g...

...# > Severity set to 'serious' from 'normal' > severity 539409 normal Bug #539409 [ejabberd] ejabberd: ipv6 nameservers in resolv.conf breaks SRV lookups Severity set to 'normal' from 'serious' > ## > > severity 547300 serious > ## > Bug #547300 [bitlbee] does not use ipv6 connection to jabber server > ## > Severity set to 'serious' from 'normal' > severity 547300 normal Bug #547300 [bitlbee] does not use ipv6 connection to jabber server Severity set to 'normal' from 'serious' > ## > > severity 551...

...iguration on managed interface Severity set to 'serious' from 'normal' > severity 539409 serious Bug #539409 [ejabberd] ejabberd: ipv6 nameservers in resolv.conf breaks SRV lookups Severity set to 'serious' from 'normal' > severity 547300 serious Bug #547300 [bitlbee] does not use ipv6 connection to jabber server Severity set to 'serious' from 'normal' > severity 551937 serious Bug #551937 [linux-2.6] iproute: "ip -6 route replace ..." behaves as "ip -6 route add ..." Severity set to 'serious' from 'normal...