Bug 232 - Startup fails with RPM install on linux: mkdir /usr/local/slimserver/Cache: Permission denied at /usr/local/slimserver/CPAN/Template/Provider.pm line 377
: Startup fails with RPM install on linux: mkdir /usr/local/slimserver/Cache: P...
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 5.x or older
: Other RedHat Linux
: P1 blocker (vote)
: ---
Assigned To: Robert Moser II
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-04-03 11:23 UTC by Blackketter Dean
Modified: 2008-12-18 11:49 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blackketter Dean 2004-04-03 11:23:15 UTC
The RPM install fails to start because the user slimserver can't create a Cache directory for the 
templates.  There are probably a couple of things to fix here: 
1.  Don't make this a fatal error (let it cache in RAM if it can't write it out.)
2.  Make that directory during the install with the correct permissions.
Comment 1 KDF 2004-04-04 13:53:48 UTC
If you create a Cache dir in cvs, should the RPM build not automatically include
that when it creates the RPM?  This way, the directory is already there along
with the rest and no fiddling with the spec file is required.
Comment 2 Blackketter Dean 2004-04-05 07:47:05 UTC
Yes, but that only solves it for Linux.  I'm not sure that this is the right place for windows or mac to 
cache.  Plus the server should handle this gracefully if the permissions prevent it.  

Robert: you willing to take a look at this?
Comment 3 Robert Moser II 2004-04-05 08:15:09 UTC
I'm not sure adding Cache to CVS is appropriate, nor do I think it would solve
the permissions problem.  Instead of failing when it attempts to create Cache,
it would fail when it attempts to create the first subdirectory under Cache.

The permissions could most likely be worked out in the RPM build itself, and
that seems to me to be the correct location to do it.

For Windows, I think that the current location for the Cache directory is the
correct one.  I don't have an opinion for Mac.

It shouldn't be too difficult to put together a check to confirm writability of
the Cache directory.  I'll throw something together for tonight.
Comment 4 KDF 2004-08-27 15:41:53 UTC
I'm thinking this one was fixed 4 months ago?
Comment 5 Chris Owens 2006-06-16 14:39:42 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Comment 6 Chris Owens 2008-10-02 15:03:24 UTC
Long list of versions is confusing for new bug filers.
Comment 7 Chris Owens 2008-12-18 11:49:54 UTC
Routine bug db maintenance; removing old versions which cause confusion.  I apologize for the inconvenience.