Suggested method for dealing with logging facilities
Daniel J. Luke
dluke at geeklair.net
Thu Aug 12 07:04:15 PDT 2010
On Aug 12, 2010, at 10:02 AM, Daniel J. Luke wrote:
> On Aug 12, 2010, at 12:03 AM, Scott Haneda wrote:
>> If an app has built in logging facilities for local0, local1...local7, and daemon, and by default set to log to /var/log/messages what is the MacPorts suggested resolution to this?
>>
>> Creating /var/log/messages will not start the logging as there is no facility for it. You would have to edit /etc/syslog.conf, which could change via software update.
>>
>> The only thing I am coming up with is source modification in the PortFile, which would allow me to set it to /opt/loccal/var/log or to /var/log/system.log
>>
>> This is for smartmontools in case anyone is familiar with that.
>
> Honestly, I would just leave it alone.
>
> If a person installing the port wants logging, he/she can update /etc/syslog.conf
>
> Software updates don't usually touch /etc/syslog.conf (and if they do, it's really a bug as Apple shouldn't be overwriting that file).
oh, also the man page says it logs to /var/log/messages but it just says that because the author uses a linux system... (it actually just uses syslog and syslog will send it to whatever file it is configured for via syslog.conf)
--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
More information about the macports-dev
mailing list