logging: Ensure journald identifier is simply "cc-proxy"

[jodh-intel]

Previously, the identifier used for each proxy log message specified
the full path to the proxy binary. This meant that to select proxy log
messages it was necessary to specify:

$ sudo journalctl -t /usr/libexec/clear-containers/cc-proxy

Now, the user can perform the same action with a simple:

$ sudo journalctl -t cc-proxy

Fixes #180.

Signed-off-by: James O. D. Hunt james.o.hunt@intel.com

[clearcontainersbot]

kubernetes qa-passed 👍

[grahamwhaley]

good catch
lgtm

[grahamwhaley]

just a thought - are there any scripts or tools that do log scraping and collating we need to update to match this ?

[jodh-intel]

Good question. The still-unfinished clearcontainers/tests#590 circumvents the issue by requiring the user to pass the required journal extracts.

@sboeuf, @chavafg - can you check for anything else that might be impacted by this?

[chavafg]

@jodh-intel, @grahamwhaley we use sudo journalctl -u cc-proxy in the teardown.sh script, so we are fine. :)

[jodh-intel]

@chavafg - actually, "yes and no" - that now needs to be sudo journalctl -t cc-proxy due to clearcontainers/runtime#835. We still launch the system-level cc-proxy instance, but it's inert and we'll be removing that soon when #177 lands.

[chavafg]

ohh, that's true, forgot about that change, then I'll open a PR to update it.

[jodh-intel]

Thanks!