search

opentechinstitute / commotion-linux-py

DEPRECATED, see commotion-client - Python implementation of core commotion functions for Linux
Other
3 stars 5 forks source link

Move log location #1

Closed areynold closed 11 years ago

areynold commented 11 years ago

Log location should be moved from /tmp to linux standard /var/log

jheretic commented 11 years ago

Ideally, let's use standard logging functions so that it goes to syslog or wherever. Also, do we need this issue in all of the Linux projects? Where is logging actually happening? If it's happening all over the place, then we should probably add a logging function into commotion-linux-py and then have everything call that.

dismantl commented 11 years ago

I use syslog for commotion-service-manager.

jheretic commented 11 years ago

Which is totally the right way to go. I'm mostly concerned that there seems to be an issue identical to this one in all three python-based commotion-linux projects (commotion-linux-py, commotion-mesh-applet, and nm-dispatcher-olsrd), which implies to me that they're all using duplicate logging functionality. Seeking more clarification from @technosopher or @areynold before marking them all duplicates.

technosopher commented 11 years ago

I've been in the process of doing everything described above for a while, and just finished overhaul all of the modules to use a unified logging function in commotion-linux-py that dumps all output to syslog with custom prefixes depending on what module produced it. The changes can be seen in the decompose branches of nm-dispatcher-olsrd and commotion-mesh-applet

technosopher commented 11 years ago

Starting work on this now.

(This message brought to you by Hub board)

technosopher commented 11 years ago

This work is complete.

(This message brought to you by Hub board)

technosopher commented 11 years ago

This work is complete.

(This message brought to you by Hub board)