19:13:19 <warden> tux0r, thanks! I can't remain alwoys online, but I read the transcript in https://log.omnios.org/omnios/ (I'm not an avid IRC user)
19:16:29 <warden> If I understood right, OmniOS has bot syslog and rsyslog, but only the latter is active, so I added a file in /etc/rsyslog.d/ with this line: "auth.notice /var/log/authlog" and restarted the rsyslog service, but the log file is still empty. What I'm missing?
19:17:27 <warden> ^bot^both :)
19:29:24 <jclulow> warden: What messages are you expecting to see at the "auth.notice" level?
19:30:21 <jclulow> It looks like sshd emits publickey/disconnect messages at auth.info
19:30:58 <jclulow> Which is a lower severity than notice, so you'd have to specify "auth.info" instead
19:31:20 <jclulow> It looks like the default for for "LogLevel" in sshd_config is INFO, which matches up
19:41:12 <warden> I tried also matching auth.*, but nothing. But, hey! ... I just noticed that rsyslog was in "mainteinance mode since yesterday, because of a typo I entered in one of my tries! :S
19:42:04 <warden> so each time I launched "svcadm restart rsyslog" I was doing nothing actually... but the command didn't output any error
19:43:13 <warden> I just noticed this by looking in /var/svc/log/system-system-log\:rsyslog.log (and then with fmdump(8))
19:44:29 <warden> I think that fault management is a wonderful feature, but it didn't actively notified me of the problem, neither the output of svcadm(8).
19:45:42 <warden> In FreeBSD, if I try to restart a service that is down it immediately tells me "[servicename] not running? (check /var/run/[servicename].pid)"
19:47:43 <warden> I'm not saying that it's wrong in OmniOS, but I'd wish to know what I was missing... for example: maybe I should have configured the fault management system to notify the admin via email such type of problems?
19:48:07 <andyf> One very useful command is `svcs -x` which shows any services which are in the degraded or maintenance states.
19:48:16 <m1ari> `svcs -xv` can be your friend
19:48:25 <andyf> You can configure email notifications too, or snmp if I remember correctly.
19:55:33 <warden> ok, I'm reading fmd(8)... any switch to add to svcadm to sending something on stderr or interactive output when a stupid admin try to restart a service which is inactive or faulty?
19:57:15 <warden> well, maybe the response is in my own question.... I;m stupid because I'm still accustomized to the idea that a service has to be started/stopped, and not enabled/disabled! ;)
19:59:20 <warden> rc(8) is definitely a far less complex/featured than SMF(7)... :)
19:59:49 <andyf> I don't know of any switch, but some kind of warning output is not a bad idea when retarting a maintenance server!
19:59:51 <andyf> *service
20:19:01 <warden> andyf: it would be surely helpful for novices... thanks! :)
23:16:13 <jclulow> warden: If you do "svcadm enable -s system-log" it will emit a warning like: svcadm: Instance "svc:/system/system-log:default" is in maintenance state.
23:16:24 <jclulow> -s means "synchronous", or "wait for it to reach the online state"
23:16:46 <jclulow> Probably "svcadm refresh" and "svcadm restart" should print a similar warning if something is in the maintenance state.  I'll file a bug