Changed back to
Code:
SLIMOPTIONS=""
CACHEDIR=/new location/logitechmediaserver/cache
restarted lms service and rescanned... again with succes...
Thx again for the help!!
THildebrandt wrote:
> so - keeping
> >
Code:
> > SLIMOPTIONS=""
> CACHEDIR=/new location/logitechmediaserver/cache
> >
> should yield the same results??
>
> Meaning the reason it works now is the removal of
> >
Code:
>
BosseJ wrote:
> Roland0 advised (correctly) against setting the SLIMOPTIONS variable to
> "--cachedir /new location/logitechmediaserver/cache". See item #13 in
> this thread.
> It may work now but you have a start command that has two "--cachedir"
> directives and it may cause problems in some f
THildebrandt wrote:
> Checked server.prefs for 'librarycachedir' and it was already pointin to
> the new cahce dir.
>
> I then:
> stopped lms service
> erased the entry in server.prefs: dbsource:
> dbi:SQLite:dbname=/var/lib/squeezeboxserver/cache/library.db
> and changed
> >
Code:
---
Checked server.prefs for 'librarycachedir' and it was already pointin to
the new cahce dir.
I then:
stopped lms service
erased the entry in server.prefs: dbsource:
dbi:SQLite:dbname=/var/lib/squeezeboxserver/cache/library.db
and changed
Code:
SLIMOPTIONS=""
CACHEDIR=/
There's another pref "librarycachedir" which is being generated upon
first start (IIRC). That's what's being used for the library files. You
How do i reset this??
Edit server.prefs to make it point to where you want it to be. Then
delete the dbsource line you quoted earlier.
--
Michael
___
THildebrandt wrote:
> 1st: no - my error, persist both places with lower case p...
> 2nd: server.pref contains this line referencing the old cache location:
> dbsource: dbi:SQLite:dbname=/var/lib/squeezeboxserver/cache/library.db
>
> 2nd point may very well be the culprit... but how to change?
Roland0 wrote:
> Depending on which music importers are used, LMS either uses it's
> internal scanner, or runs scanner.pl as an external process.
> Maybe one of the two uses the old location, the other the new. Why this
> happens, I have no clue.
> Things you could try:
> - check if any entry in
mherger wrote:
> > Maybe one of the two uses the old location, the other the new. Why
> this
> > happens, I have no clue.
>
> There's another pref "librarycachedir" which is being generated upon
> first start (IIRC). That's what's being used for the library files. You
>
> might need to reset
Maybe one of the two uses the old location, the other the new. Why this
happens, I have no clue.
There's another pref "librarycachedir" which is being generated upon
first start (IIRC). That's what's being used for the library files. You
might need to reset its value before restarting LMS with
BosseJ wrote:
>
> you could try
> >
Code:
> > SLIMOPTIONS="--cachedir /new location/logitechmediaserver/cache"
> >
>
I'd advise against this - you'll end up with two "--cachedir" arguments
(since the script already passes --cachedir $CACHEDIR)
THildebrandt wrote:
> At the moment the server runs, scanning without problems... the only
> 'problem' is that for some reason sqllite db are created on the old AND
> the new cache dir...
>
>
Depending on which music importers are used, LMS either uses it's
internal scanner, or runs scanner.p
THildebrandt wrote:
> At the moment the server runs, scanning without problems... the only
> 'problem' is that for some reason sqllite db are created on the old AND
> the new cache dir...
>
> Any ideas why this happens??? Obviously i would prefer that only the new
> cachedir is used...
>
> Thx
At the moment the server runs, scanning without problems... the only
'problem' is that for some reason sqllite db are created on the old AND
the new cache dir...
Any ideas why this happens??? Obviously i would prefer that only the new
cachedir is used...
Thx...
---
So...
Ensured user squeezeboxserver had rights to the new cache dir...
Stopped service, deleted old cachedir (but this time i left in the
various directories - DownloadedPlugins, InstalledPlugins...) after
copying everything to new cachedir, restarted service..
Then when opening the server page
Looking through server.prefs for squeezeboxserver it looks as though the
sqlite db still needs to be in the original cache directory???
Any idea how i move this to new location???
THildebrandt's Profile: http://forums.sli
THildebrandt wrote:
> Suggestions??
Check the LMS server / scanner log (WebUI > Sessings > Information)
What file system is the cache on? Looks like a remote one - never a good
idea (slow, potentially unstable due to network fluctuations - if it's
SMB, even more problematic).
Finally, check per
Looks like it didnt work after all...
Thinking i could remove the old cachedir now that a new has been
definded (copied the old to the new location, of course) i now get this
result when initiating scan of my music library:
Code:
service logitechmediaserver status
●
Once i got rid of the spelling errors this seems to work:
Code:
# User to run Logitech Media Server as
SLIMUSER=squeezeboxserver
SLIMOPTIONS=""
CACHEDIR=/new location/logitechmediaserver/cache
Thank you!
Roland0 wrote:
> For debian / ubuntu, the file to edit would be
> /etc/default/logitechmediaserver
/etc/default/logitechmediaserver edited from
Code:
# User to run Logitech Media Server as
SLIMUSER=squeezeboxserver
SLIMOPTIONS=""
to
Code
THildebrandt wrote:
>
> New installation of openmediavault; installed LMS 7.9.1 flawlessly.
> I want to move the location of the cache to other drive; tried editing
> server.pref without luck, broke LMS requiring new installation...
>
setting cachedir in server.pref isn't a good idea, as it wi
Hello!
New installation of openmediavault; installed LMS 7.9.1 flawlessly.
I want to move the location of the cache to other drive; tried editing
server.pref without luck, broke LMS requiring new installation...
Somewhere i stumbled across a reference til specifying the cachedir by
adding an ar
22 matches
Mail list logo