similar to: NSS support in trunk (was: NSS branch pull request)

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

2015-03-26 9:03 GMT+01:00 Arnaud Quette <arnaud.quette at gmail.com>: > Hey mister M' > > A first huge thanks for taking care of this, and so late in the night. I > know that it's not easy... > > (sent from my S3... please excuse my brevity) > Le 25 mars 2015 18:49, "Emilien Kia" <kiae.dev at gmail.com> a ?crit : > > > > > >

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

Hello all, I come back to request comments (and merge) on my pull request of the libnutclient. https://github.com/clepple/nut/pull/2 All previous comments have been addressed (some fixes and documentation). For memory, the libnutclient is an high-level C++ and C client library allowing to dialog with upsd. The addressed model is oriented around devices, variables and commands; unlike

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

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

Hello All 2015-03-26 9:03 GMT+01:00 Arnaud Quette <arnaud.quette at gmail.com>: > > > What I will do is to move ssl initializing after usering and forking, > than add key file right checking where ssl was initialized before (before > forking). > > As keys should be owned by nut user, this would not be a problem. > > And moving this code, independently of SSL

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

Hi Charles and the list here is an update on 2.7.3 2015-03-20 3:33 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 19, 2015, at 2:00 PM, Arnaud Quette <arnaud.quette at gmail.com> > wrote: > > * #158: the branch has been collapsed into one commit, but additional >> documentation (nut-names.txt) is needed: >>

?Hello everybody, just a few notes to the doxygen X man issue: 1/ AFAIK doxygen can generate man pages, so why don't we just generate them and decide then whether they are ill fitted or usable... 2/ I'd definitely use doxygen when possible; I mean I don't know any alternative that's able to do (at least partial) validation of the documentation with the source 3/ I

Is it ok sending this results for FreeBSD5.1 at daily/weekly based to this mail list? Now results. Big improvement in llvm tests results from last test result sended. New regressions: Regression.Assembler.ConstantExprFold : FAIL , expected PASS Regression.CodeGen.Generic.2004-04-09-SameValueCoalescing: FAIL , expected PASS Regression.Transforms.PRE.basictest : FAIL

>Your "make check" output has two classes of errors: >1. llvm-gcc or llvm-g++ not being found. Its possible this results from >Cygwin requiring the .exe extension. The makefiles probably need to be >enhanced to include the suffix. Okay, but that did not seem to be a problem before. I thought about that being a possible problem. The make install removes the .exe

Dear fellows, As you have probably seen, NUT has had a recent boost through the help of Eaton. Frederic Bohe (contractor for Eaton France) has worked on Augeas, and is now working the Windows port. Chetan Agarwal, seconded by Prashi Gandi (both from Eaton India) are working on XCP and quality / validation related projects. I'm now pleased to announce that Emilien Kia (contractor for Eaton

2015-04-27 15:02 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Apr 27, 2015, at 2:48 AM, Nick Ma. <nick.mayerhofer at enchant.at> wrote: > > > But it still doesn't compile any executable: ~/nut/tests% ls > > cpputest.cpp example.cpp Makefile Makefile.am Makefile.in > > I think it is only intended to produce an executable when running "make

Hi, I have a customer testcase where SROA splits a volatile memcpy and we end up generating bad code[1]. While this looks like a bug, simply preventing SROA from splitting volatile memory intrinsics causes basictest.ll for SROA to fail. Not only that, but it also seems like handling of volatile memory transfers was done with some intent. What are the design decisions in SROA regarding

On 11/10/2015 1:07 PM, Joerg Sonnenberger via llvm-dev wrote: > On Tue, Nov 10, 2015 at 10:41:06AM -0600, Krzysztof Parzyszek via llvm-dev wrote: >> I have a customer testcase where SROA splits a volatile memcpy and we end up >> generating bad code[1]. While this looks like a bug, simply preventing SROA >> from splitting volatile memory intrinsics causes basictest.ll for SROA

Your "make check" output has two classes of errors: 1. llvm-gcc or llvm-g++ not being found. Its possible this results from Cygwin requiring the .exe extension. The makefiles probably need to be enhanced to include the suffix. 2. You have a permissions problem on: test/Regression/Analysis/Andersens/Output/basictest.ll.out.script. The file couldn't be opened for writing. Possibly

Hey mister M' A first huge thanks for taking care of this, and so late in the night. I know that it's not easy... (sent from my S3... please excuse my brevity) Le 25 mars 2015 18:49, "Emilien Kia" <kiae.dev at gmail.com> a ?crit : > > > > 2015-03-21 17:06 GMT+01:00 Melkor Lord <melkor.lord at gmail.com>: >> >> >> On Fri, Mar 20, 2015

[I took the liberty of replying on nut-upsdev - not many people are using github yet since the NUT repository native format is still SVN.] On Sep 4, 2012, at 10:17 AM, Emilien Kia wrote: > This is a proposal for a new client library which scopes an higher level than the existing libupsclient. > > It needs less dependencies to be compiled than the libupsclient and can be easier to

Hi all, I am pleased to announce that NSS port of NUT is finished. Port is fully functionnal (same functionnalities as openssl, and a not-activated-by-default client certificate validation function) and successfully tested by myself (external tests are pending, Frederic Bohe is planned for) with a test matrix which will be uploaded to the web site soon (by Arnaud), tested functionnality by