On 02/03/10 09:47, Paul Willis wrote:
> I need to configure system-log to disable logging from a remote host.
> To do so I use the following command:
>
> svccfg -s [b]svc:/system/system-log[/b] "setprop config/log_from_remote = 
> [b]false[/b]"
>
> I noticed that when I run the command,
> svcprop -p config/log_from_remote [b]system-log[/b]
> or
> svcprop -p config/log_from_remote [b]system-log:defaut[/b]
> or
> svcprop -p config/log_from_remote [b]svc:/system/system-log:default[/b]
> they all return true.
>
> However, when I run the command,
> svcprop -p config/log_from_remote [b]svc:/system/system-log[/b], it returns 
> false.

   The first three all return the value currently in use by the service
   instance (the first two names are considered aliases for full FMRI
   used in the third invocation), whereas the last one returns the value
   set on the service.

> I also tried the command:
> svccfg -s [b]svc:/system/system-log:default[/b] "setprop 
> config/log_from_remote = false"
> It does not work, returns: svccfg: No such property group "config".
>
> Can anyone explain why the differences?
> I am presuming that I should use "svc:/system/system-log" for both svccfg and 
> svcprop.  Is this correct?

   The property is defined by the service.  You can set it there where
   it will be inherited by all the service's instances (of which there
   is probably only one).  Or you can create the property group in the
   instance and override the setting there.  Either way, once you've
   made the change you need to 'svcadm refresh' to tell the system you
   are done making changes and the service should consume the new
   configuration.

   From the look of things, you have already set log_from_remote to
   false on the service, and you just need to refresh for the instance
   to see the change.  (Unfortunately, syslog doesn't appear to reread
   that property when refresh, so you may need to 'svcadm restart' after
   you've refreshed the instance.)

   Dave

Reply via email to