On 02/14/2014 12:20 PM, Dave Brolley wrote:
There is still one outstanding problem which is affecting quite a few
tests (039 046 053 085 161 178 234 242 248 304 352 354 466 524 593
650). The problem occurs when pmlogger is running as a normal user. In
that case, pmlogger is unable to bind to (i.e. create) the unix domain
socket in /var/run/pcp because that directory is not writable by
normal users (drwxrwxr-x. 2 pcp pcp). Perhaps another location in that
case?
The commit below handles this ... (pcpfans brolley/dev)
commit 3685cfa7480a900e6df591762cd79a06467204ac
Author: Dave Brolley <brolley@xxxxxxxxxx>
Date: Mon Feb 17 11:37:53 2014 -0500
Handle unix domain socket binding (creation) for pmlogger when run
as a normal user.
When running as a normal user, pmlogger is unable to bind to
(i.e. create) a unix domain socket in /var/run/pcp (PCP_RUN_DIR),
because that directory is not writable by normal users. This change
handles
the situation in a similar way to how the port map file in
/var/lib/pcp/tmp/pmlogger (PCP_TMP_DIR)/pmlogger is handled, which
is to
continue on and to issue a message only if DESPARATE is defined
at compile time.
This solution is reasonable, since pmlogger will go on to create
inet and ipv6 sockets for control connections. Only if all
sockets fail to bind is this a critical error.
This addresses the regression of qa tests 039 046 053 085 161 178
234 242 248 304 352 354 466 524 593 and 650.
|