| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 974] Installation issues when user "pcp" and/or group "pcp" already defined |
| From: | bugzilla-daemon@xxxxxxxxxxx |
| Date: | Fri, 10 May 2013 00:04:20 +0000 |
| Auto-submitted: | auto-generated |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <bug-974-835@xxxxxxxxxxxxxxxx/bugzilla/> |
| References: | <bug-974-835@xxxxxxxxxxxxxxxx/bugzilla/> |
Nathan Scott
changed
bug 974
Comment # 1
on bug 974
from Nathan Scott
On upgrade, I don't think there's any way to distinguish between a pcp user created by an earlier pcp rpm install and one created by an admin. Personally, I think we do the best we can given the packaging tools available - and we also do the same thing that other packages in the same boat are doing. And the PCP_USER does allow overriding this, so I'm not sure there's really a whole lot of improvement that can happen here ... do you have anything further in mind Ken? re the PCP_GROUP setting, we currently do a getpwent(3) lookup on the PCP_USER account, and take the uid and gid settings from there ... again, this seems like a pretty good option to me, and not clear that further complicating things with additional configuration options is a win. cheers. You are receiving this mail because:
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pcp updates - assorted non-trivial changes, Ken McDonell |
|---|---|
| Next by Date: | pcp updates: scox merge, dbpmda auth support, misc qa, Nathan Scott |
| Previous by Thread: | [Bug 974] New: Installation issues when user "pcp" and/or group "pcp" already defined, bugzilla-daemon |
| Next by Thread: | [Bug 974] Installation issues when user "pcp" and/or group "pcp" already defined, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |