Switching emonpi/emoncms logfile locations to /var/log/emoncms

[TrystanLea]

@TrystanLea

The main issue I can see is that switching to this approach right now will mean that all emoncms logs will move to the /var/log tmpfs partition and so will cease to be persistent on existing images. The main log likely to be of concern is the emonpiupdate.log which should ideally be persisted. This could be solved with a symlink, but the symlink would need to be created at system startup, probably not a big issue.

I’ve got this appraoch working, it requires the creation of the /var/log/emoncms directory in rc.local and then lower down in rc.local:

chown -R pi:pi /var/log/emoncms
touch /home/pi/data/emonpiupdate.log
ln -s /home/pi/data/emonpiupdate.log /var/log/emoncms/emonpiupdate.log

touch creates the file if it doesnt exist and leaves it be if it does.

This is only needed for older images of course and the new image rc.local is the default with no changes + log2ram handles persistance.

Once this is in place Im ready to merge the log_location branches of emoncms and modules ready for the new script release: emonSD next steps: filesystem & logrotate - #192 by TrystanLea