[MacPorts] #25613: smartmontools 5.39.1 Logging does not function
MacPorts
noreply at macports.org
Sat Jul 10 03:29:16 PDT 2010
#25613: smartmontools 5.39.1 Logging does not function
------------------------------------------------+---------------------------
Reporter: scott@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Keywords: log, syslog, smartd, smartmontools | Port: smartmontools
------------------------------------------------+---------------------------
smartmontools is a package that contains `smartctl` and `smartd`, this
report is in regards to `smartd` only.
All documentation states that logging messages will be sent to 'SYSLOG'.
The [http://smartmontools.sourceforge.net/man/smartd.8.html smartd man
page] specifically states:
> -l FACILITY, --logfacility=FACILITY
> Uses syslog facility FACILITY to log the messages from smartd. Here
FACILITY is one of local0, local1, ..., local7, or daemon [default]. If
this command-line option is not used, then by default messages from smartd
are logged to the facility daemon.
Further, emails generated for alert or testing state:
> For details see host's SYSLOG (default: /var/log/messages).
Nothing as far as I can tell is sent to /var/log/system.log. I believe
that would be the correct place for this. If another location was
determined to be in for example /opt/local/var/log/smartmontools.log then
an entire syslog mechanism would have to be installed and configured along
with it.
According to the snip above, 'daemon' is the default, which Mac OS X does
not have a logging channel for. What is the correct procedure to solve
this? Not everyone will use the mail feature of smartd to get an alert,
and I think it is important to also have this logged to syslog. Not
everyone has `mail` functioning on their local systems.
Ideally, no edits would need to be made to /etc/syslog.conf. Is this
simply a matter of altering the launcd item to add --logfacility=notice ?
I spent a bit of time trying to figure out if this software was even
working, to learn that my mta was off. This would have been logged to
syslog, which I was `tail -f`ing just as I -HUP'd `smartd`, but nothing
showed up. I browsed the source a little to see if I thought it was
solvable there, or with a configure arg, but I don't believe that to be
the case.
This is not my area of expertise, but if someone can tell the correct
approach to fixing it, I would like to give it a try. I would also like
to try to add in a +growl variant for instant alerts on screen which has
it's own mail feature as well.
--
Ticket URL: <http://trac.macports.org/ticket/25613>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list