You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
possible problem: on "light", dedicated player systems using SD/CF/SSD or other flash media, I always set the /var/log (as well as /tmp and /var/tmp) file system to be on a RAMdisk. Among the other things, that way I avoid excessive (re)writing on the flash.
Obviously, when the system starts /var/log is empty. Any software expecting to find an existing log dir in there may/will fail. Please make sure that falcon will automatically re-create any missing dir it may require under /var/log upon startup.
(if falcon does not expect/require any dir to exists under /var/log, please ignore this issue).
The text was updated successfully, but these errors were encountered:
Problem here are permissions:
/var/log is normally write protected, sure against www users, so,
during installation, falcon creates a special directory /var/log/falcon with
granted write permission to www-data, same for var/log/squeezelite and user
squeezelite.
This way www-data could write to existing files, create new, delete old, rename, rotate,.. in a 'secure' way (or better, maybe secure enought for a music player in a lan).
Same for squeezelite, but here you could also choose a completely different location for the log file (i.e. /var/log/falcon) directly on the web gui.
You could change configuration for your installation, but I think you better mount /var/log/falcon and maybe also /var/log/squeezelite on RAM disk instead.
p.s.
If you are thinking to build up quite a sort of a distribution, name it and adjust falcon script until it will completely fit your requirement. Probably is a matter of changing few rows in the configuration file and - maybe a couple of scripts.
Is the way falcon is built, Should be very, very simple.
Hi Marco,
possible problem: on "light", dedicated player systems using SD/CF/SSD or other flash media, I always set the /var/log (as well as /tmp and /var/tmp) file system to be on a RAMdisk. Among the other things, that way I avoid excessive (re)writing on the flash.
Obviously, when the system starts /var/log is empty. Any software expecting to find an existing log dir in there may/will fail. Please make sure that falcon will automatically re-create any missing dir it may require under /var/log upon startup.
(if falcon does not expect/require any dir to exists under /var/log, please ignore this issue).
The text was updated successfully, but these errors were encountered: