You are setting up a local IPS package repository on your Oracle Solaris11 server: solaris.example.com. You want to point the existing local IPS publisher to the new local IPS repository located in…

Question

Options

• AIssue the pkgrepo refresh -s command to refresh the repository.
• BRestart the svc:/application/pkg/server:default service.
• Cpkg set-publisher command to set the new repository location.
• DIssue the pkgrepo rebuild command to rebuild the repository.
• EIssue the pkgrepo set command to set the new repository location.

• A
  6% (2)
• B
  3% (1)
• C
  75% (24)
• D
  3% (1)
• E
  13% (4)

Explanation

Option C is correct because the scenario shows the repository server is already running and properly configured - the service is online, /repo has the correct structure, and the service properties point to /repo - but pkg publisher shows no URI, meaning the client-side publisher has not yet been told where the repository lives. The command pkg set-publisher -g http://solaris.example.com solaris (or equivalent) registers that URI with the pkg(1) client, which is the missing step.

Why the distractors are wrong:

• A (pkgrepo refresh) refreshes the repository's catalog metadata - useful after adding packages, but the repo structure is already intact and the service is online.
• B (restart the service) is unnecessary because svcs already shows the service is online; restarting it changes nothing about the publisher URI the client sees.
• D (pkgrepo rebuild) reconstructs the search index and catalog from package manifests - a recovery tool, not a publisher configuration step.
• E (pkgrepo set) configures properties inside the repository itself (e.g., setting the publisher name in the repo), not the client's pointer to that repository.

Memory tip: Think server-side vs. client-side. pkgrepo commands operate on the repository; pkg set-publisher operates on the client - once the server is running, you still need to tell the client where to look.

No community discussion yet for this question.