| To: | PCP Mailing List <pcp@xxxxxxxxxxx> |
|---|---|
| Subject: | PCP Updates: Fix Bug #1035: PMCD Should Not Fail to Start if NSS Fails to Initialize |
| From: | Dave Brolley <brolley@xxxxxxxxxx> |
| Date: | Tue, 25 Mar 2014 11:00:39 -0400 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 |
Branch brolley/dev in pcpfans.
--------------------------------------------------------------------------
commit b9d2adfa5ae7cc5d8ef8416bbf804736a40efda5
Author: Dave Brolley <brolley@xxxxxxxxxx>
Date: Tue Mar 25 10:35:25 2014 -0400
When NSS fails to initialize, pmcd should still start successfully.
oss.sgi.com/bugzilla/show_bug.cgi?id=1035
Previously, pmcd would fail to start if NSS failed to start or
if a suitable certificate could not be established for secure
connections. With this change, pmcd will start under these
conditions, but will not accept secure connections.
New qa test 966 checks that pmcd starts and accepts non-secure
connections.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 1035] PMCD Should Not Fail to Start if NSS Fails to Initialize, bugzilla-daemon |
|---|---|
| Next by Date: | [Bug 1035] PMCD Should Not Fail to Start if NSS Fails to Initialize, bugzilla-daemon |
| Previous by Thread: | [Bug 1035] PMCD Should Not Fail to Start if NSS Fails to Initialize, bugzilla-daemon |
| Next by Thread: | Re: PCP Updates: Fix Bug #1035: PMCD Should Not Fail to Start if NSS Fails to Initialize, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |