search for: l1008

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 intend to look more deeply. Best regards, Emilien 2015-03-13 13:30 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 12, 2015, at 11:55 P...

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

W dniu 24.08.2018 o 13:10, Charles Lepple pisze: > Sorry, I didn't mean to imply that the master branch was necessarily going to be different, just wanted to make sure you had everything set up to recompile. The real test is to see if things change after commenting out that line (such as by changing it to start with "//"): > > // { "shutdown.return", 0, 0,

...t gmail.com>: > 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 intend to look more deeply. > > Best regards, > > Emilien > > > 2015-03-13 13:30 GMT+01:00 Charles Lepple <clep...