Bugzilla – Bug 15252
TinySC logs should be available via Samba
Last modified: 2010-04-08 17:25:55 UTC
Either we need to log to the media, or export /var/log over Samba as read-only. Logs are going to syslog now, I wonder if this will be OK or if we need a separate server.log. Maybe we can configure this with syslog?
Vahid says he will have a look
In the meantime, is it possible to move the logdir to /media/sda1? If so, how is it done?
The configuration files for the samba are located under /etc/samba/. It seems to me that by adding the /var/log as a share point in the /etc/samba/smb.conf the log files could be accessed.
(In reply to comment #3) > It seems to me that by adding the /var/log as a share point in the > /etc/samba/smb.conf the log files could be accessed. I tried that, but it looks like smb.conf is overwritten at boot time. Is that really necessary?
The smb.conf is overwritten by the samba program whenever it starts. The key is changing the samab to add the logs as a read-only folder. I made the necessary changes in samab script and I will commit it by tomorrow.
Ah, ok... It looks like the /etc/init.d/samba script builds smb.conf from smb.conf.dist. You just need to edit smb.conf.dist, not change the script. Now what about moving server and squeezeplay logging out of syslog?
Not sure about that. The .dist is just a template, so the smb.conf is built based on the template. I think that the samba script should be changed to add it to the share points.
I am ready to commit my changes that exports the /var/log as a read-only folder. Is it good enough to consider this bug fixed?
I checked in the code that exports the /var/log directory as a read-only folder. This should enable the monitoring of the log files including the samba logs.
We're not going to address breaking the SP and SbS logging out of the syslog into their own log(s)?
I leave the decision to Chris. The changes I made will fix this bug. If he thinks it is necessary to keep them in a separate logs, then we may want to create a new bug to track it.
Should this be seen in the current firmware? I'm not seeing the share.
Please try 7.5.0.r8443. It should have the fix. I had to make some changes in poky to include my changes in the build.
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!