DJanGo wrote:
> These settings are at least since 'Aug 24, 2011'
> (https://github.com/Logitech/slimserver-platforms/blob/public/7.9/debian/logitechmediaserver.logrotate)I
> only noticed that the log file only covered a short period when
Michael asked for a log of an event the previous evening
slartibartfast wrote:
> OK maybe Spotty fills up the 200k quickly but I am sure I have seen much
> longer logs previously.
>
These settings are at least since 'Aug 24, 2011'
(https://github.com/Logitech/slimserver-platforms/blob/public/7.9/debian/logitechmediaserver.logrotate)
If you installed from a .dpkg or .rpm file you can check if the file has
been modified since install. If you used a tarball all bets are off..
-Transcoded from Matt's brain by Tapatalk-
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with
Debian+LMS 7.9.0
Music: ~1300
drmatt wrote:
> Looks fine to me. It's weekly or 200k whichever comes first, based on
> that config. Open to argument as to whether 200k is too small but it's
> working as designed.
>
>
> -Transcoded from Matt's brain by Tapatalk-OK maybe Spotty fills up the 200k
> quickly but I am sure I
slartibartfast wrote:
> Michael has said that the log file should go back to day one and the
> file size limit was 100MB. Mine only goes back two days. Is that normal.
> I am pretty sure it has been bigger in the recent past.
>
> Sent from my SM-G900F using Tapatalk
I dont believe that Michael
It's weekly or 200k whichever comes first, based on that config.
-Transcoded from Matt's brain by Tapatalk-
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with
Debian+LMS 7.9.0
Music: ~1300 CDs, as 450 GB of 16/44k FLACs. No less than 3x 24/44k
albums..
DJanGo wrote:
> That is right and should fit the most users.
>
> Remember diskspace on a sd card / some Appdisk on some NAS running lms
> is premium - my logpath for all my rpis is a ramdisk (after i am really
> sure everything works like a charm)
>
> You can edit these but be careful when
slartibartfast wrote:
> There is. Contents as follows. Doesn't look right to me.
>
> >
Code:
> > /var/log/squeezeboxserver/server.log {
> weekly *Run logrotation once a week*
> rotate 5 *Keep 5 Versions of each log*
> size 200k *When any logfile is greater than
slartibartfast wrote:
> There is. Contents as follows. Doesn't look right to me.
>
> I have identical logrotate confiig. Are you referring to that both
> "weekly" and a size ("200k") is specified as criterias for rotation &
> compression? I guess the logic is 'AND' (ie, both should be
drmatt wrote:
> Never looked but is there an etc/logrotate.d/logitechmediaserver? That's
> where rotation of the log file would be driven unless LMS does it
> itself.
>
>
> -Transcoded from Matt's brain by Tapatalk-
There is. Contents as follows. Doesn't look right to me.
Code:
Never looked but is there an etc/logrotate.d/logitechmediaserver? That's
where rotation of the log file would be driven unless LMS does it
itself.
-Transcoded from Matt's brain by Tapatalk-
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with
Debian+LMS 7.9.0
Music: ~1300
I have recently noticed that my server.log file only goes back a couple
of days and it is really small. I am sure this is new behaviour. The
contents of my log folder on a Raspberry Pi looks like this
24437
Are the *.gz files significant and why do they only start on the 20th
January?
12 matches
Mail list logo