| To: | Dave Brolley <brolley@xxxxxxxxxx> |
|---|---|
| Subject: | Re: PCP Updates: Fix Bug #1035: PMCD Should Not Fail to Start if NSS Fails to Initialize |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Tue, 25 Mar 2014 12:45:29 -0400 |
| Cc: | PCP Mailing List <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <53319A17.6060608@xxxxxxxxxx> (Dave Brolley's message of "Tue, 25 Mar 2014 11:00:39 -0400") |
| References: | <53319A17.6060608@xxxxxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
Dave Brolley <brolley@xxxxxxxxxx> writes: > 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. > [...] Have you considered doing this at the pmcd/pmproxy.c level instead, so that a bad rc from __pmSecureServerSetup is sent but tolerated (instead of triggering DontStart())? That way, the __pmSecureServerSetup function doesn't lie about its success, which in turn would later let us extend pmcd with a $PCP_SECURE_SOCKETS-like option to *require* ssl? - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | PCP Updates: Fix Intermittent Failure of qa tests 712, 713, 714, Dave Brolley |
|---|---|
| Next by Date: | Re: PCP Updates: Fix Bug #1035: PMCD Should Not Fail to Start if NSS Fails to Initialize, Dave Brolley |
| Previous by Thread: | PCP Updates: Fix Bug #1035: PMCD Should Not Fail to Start if NSS Fails to Initialize, Dave Brolley |
| Next by Thread: | Re: PCP Updates: Fix Bug #1035: PMCD Should Not Fail to Start if NSS Fails to Initialize, Dave Brolley |
| Indexes: | [Date] [Thread] [Top] [All Lists] |