After installing the OS, you boot the system and notice that the syslogd daemon is not accepting messages from remote systems. Which two options should you select to modify the syslogd daemon…

Question

Options

• Asvccfg -s svc:/system/system -log setprop start/exec= "syslogd -t"
• BSet the following parameter in the /etc/syslogd.conf file:
• Csvcadm enable svc:/system/system -log/config/log_from_remote
• Dsvccfg -s svc:/system/system-log setprop config/log_from_remote=true
• ESet the following parameter in the /etc/default/syslogd file:

• A
  13% (3)
• B
  8% (2)
• C
  33% (8)
• D
  46% (11)

Explanation

On Solaris, enabling remote syslog requires two complementary steps: D uses svccfg to set the SMF (Service Management Facility) property config/log_from_remote=true on the correct svc:/system/system-log service, while E sets the LOG_FROM_REMOTE=YES parameter in /etc/default/syslogd, which feeds default startup options to the daemon.

Why the distractors fail:

• A targets the wrong property (start/exec) and mangles the service FMRI with a stray space (system/system -log); modifying the exec string is not how you toggle remote acceptance.
• B points to /etc/syslogd.conf (or /etc/syslog.conf), which only maps facility/severity to destinations - it has no directive for accepting remote messages.
• C misuses svcadm enable, which starts/stops services; it cannot set service properties - that's svccfg setprop's job.

Memory tip: Both correct answers touch defaults - D sets a property default in SMF, and E edits /etc/*default*/syslogd. If an answer references the wrong command (svcadm instead of svccfg) or the wrong file (.conf instead of /etc/default/), it's a distractor.

No community discussion yet for this question.