socklog - log events notification

Set up the socklog-notify service as described in Configuration to ensure that the named pipe /var/log/socklog/.notify exists. Do not delete this file after creation.

Read disable notifications before stopping the socklog-notify service once it is started.

socklog-notify is handled by the uncat program.

how to configure log events

Make sure the account running this log service is member of the socklog group adm. If it isn't, change it now. Make sure that the socklog-notify service is running.

Redirect the standard error output stderr of multilog to the named pipe socklog-notify is reading from. To do so, insert exec 2> /var/log/socklog/.notify as second line into /service/dnscache/log/run:

  #!/bin/sh
  exec 2> /var/log/socklog/.notify
  exec setuidgid dnslog multilog t s1000000 ./main

To configure additional log events in /service/dnscache/log/main/, use the alert action e from multilog. If you want to be notified about all log entries showing stats, add a corresponding script to the multilog configuration in /service/dnscache/log/run like this:

  #!/bin/sh
  exec 2> /var/log/socklog/.notify
  exec setuidgid dnslog multilog t s1000000 ./main \
    -* '+* stats *' e

  # svc -t /service/dnscache/log

how to configure the notification

To configure the kind of notification, edit /etc/socklog/notify/run and change the prog argument of uncat to your needs. This example uses sms_client to notify:

  #!/bin/sh -e
  PIPE=/var/log/socklog/.notify
  if [ ! -p "$PIPE" ]; then mkfifo -m0620 "$PIPE"; chown log:adm "$PIPE"; fi
  exec <> "$PIPE"
  exec setuidgid log uncat -s49999 -t90 \
    sh -c 'head -c140 | sms_client pager'

  # svc -t /service/socklog-notify

Another example using wall:

  exec setuidgid log uncat -vs49999 -t180 \
    sh -c 'head | wall'

  # grep -F /var/log/socklog/.notify /service/*/log/run

  # svc -t /service/<service>/log