I (finally) upgraded from 4.x to 5.1.1.

All went well, seemingly, until I discovered that the Slimserver had
died.

Investigation seems to point to failure to create
/usr/local/slimserver/.slimserver.db (for caching, I assume).
/usr/local/slimserver/ is owned by root:root, and thus the Slimserver
is not able to create the file.

As a short-term measure, I'm chowning /usr/local/slimserver/ to
slimserver:slimserver. Once .slimserver.db is created, can a paranoid
person safely chown it back to root:root?

(This is sounding like a scene from "Being Slimserver": "Slimserver,
slimserver, slimserver:slimserver.")

Once this is done, I may get around to playing with Unicode handling in
my Copious Spare Time -- though it seems to play nicely with the web
UI, and the SliMP3 UI shows '?' characters instead of something
starting with umlauted 'y's and Icelandic thorns. So my motivation
isn't quite so high.

Thanks for all the effort put into this software --

-- S. Ben Melhuish
sben (AT) pile (DOT) org

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQF+3yZkvNOKQ0bOCEQKhzwCgwucNXSOHxv37TCnQNzLSS6 4qCOgAn1St
qpEl5dvcGYjBizCKiDvUUWyS
=6ZwN
-----END PGP SIGNATURE-----