| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 974] Installation issues when user "pcp" and/or group "pcp" already defined |
| From: | bugzilla-daemon@xxxxxxxxxxx |
| Date: | Sun, 12 May 2013 03:33:42 +0000 |
| Auto-submitted: | auto-generated |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <bug-974-835@xxxxxxxxxxxxxxxx/bugzilla/> |
| References: | <bug-974-835@xxxxxxxxxxxxxxxx/bugzilla/> |
|
Comment # 2
on bug 974
from Ken McDonell
Agreed there is no way to tell automatically. But a sys admin should be able to do _something_ and then install/upgrade the package and have the right thing happen. I think the pcp:pcp uses in the install scripts are wrong. They should use $PCP_USER and $PCP_GROUP, with values possibly coming from some sysadmin setting (e.g. in the environment when the install/upgrade is done), else failing that the default values of pcp and pcp. Setting PCP_USER in /etc/pcp.conf is not going to help if all the chown stuff in the packaging install scripts have set the uid/gid to something else. Looking up the group from getpwent for $PCP_USER is fine at run time ... I am more concerned about the account creation and ownership settings at the time of install/upgrade. You are receiving this mail because:
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pcp updates: atop, auth, qa, Ken McDonell |
|---|---|
| Next by Date: | Re: [pcp] pcp updates: atop, auth, qa, Nathan Scott |
| Previous by Thread: | [Bug 974] 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] |