#18021: logwatch 7.3.6, new port ----------------------------------+----------------------------------------- Reporter: lassi.tuura@… | Owner: snc@… Type: enhancement | Status: reopened Priority: Normal | Milestone: Port Submissions Component: ports | Version: 1.7.0 Resolution: | Keywords: Port: logwatch | ----------------------------------+----------------------------------------- Changes (by snc@…): * status: closed => reopened * resolution: fixed => Comment: Replying to [comment:12 lassi.tuura@…]:
The "ui_msg" lines refer to "dnsmasq", should this not be "logwatch"? There is also a missing "h" in "launcd". Both are on line 58. (Thanks for adding the message, I was wondering how to make one and under which circumstances.)
You're absolutely correct. I was mimicking dnsmasq's ui_msg too closely!
I also noticed the plist now runs the command directly rather than via /bin/sh. I am not sure this will work as for me logwatch needed /opt/local/bin in $PATH. Does logwatch run for you via launchd without setting $PATH? I wonder if I have some anti-dependency on my system.
I've never had an issue with running the binaries directly from launchd. You'll notice that the binary is run with it's full path to avoid the issue you likely had. Launchd confirms the event is loaded ({{{sudo launchctl list | less logwatch}}}) and will sit waiting for the designated time to occur. I did notice that, upon running the binary directly ({{{sudo logwatch}}}) there was an error: /opt/local/var/cache/logwatch No such file or directory at /opt/local/bin/logwatch line 751. It seems we need to create that directory. I'll attach a couple patches shortly showing how I intend to fix these issues. If they're satisfactory I'll apply them. -- Ticket URL: <http://trac.macports.org/ticket/18021#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS