<div dir="ltr">On Fri, Sep 20, 2013 at 11:43 AM, Gary Buhrmaster <span dir="ltr"><<a href="mailto:gary.buhrmaster@gmail.com" target="_blank">gary.buhrmaster@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Sep 20, 2013 at 4:12 PM, Richard Shaw <<a href="mailto:hobbes1069@gmail.com">hobbes1069@gmail.com</a>> wrote:<br>
....<br>
<div class="im">> True, but this is a fairly well used installation, so it's worth evaluating<br>
> if the directory can be removed.<br>
<br>
</div>However, have you ever used the video functionality?<br>
The code uses the /video/ subdir of .../data/ (in at<br>
least some of the code, for some code paths). And<br>
the git commits for the app show creating the .../data/<br>
and subdirs specifically so that the app works correctly<br>
for all cases, not just what one sees on their system.<br></blockquote><div><br></div><div>My package doesn't create the video and video_covers directories so mythweb must be handling that itself.</div><div><br></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree that one could review the app and determine<br>
if there are (now) unused subdirs based on current<br>
patches. But if that is so, one should apply the patches<br>
"upstream" (i.e. in mythweb itself).<br>
<div class="im"><br>
> Per the guidelines[1] /usr/share is preferred, though presumably that's<br>
> intended for static data...<br>
<br>
</div>Exactly. And this app is not all static data.<br>
<div class="im"><br>
> It also mentions not using /var/www because 1)<br>
> user may already have data there, and 2) it's not part of FHS anymore.<br>
<br>
</div>"base" /var/www is certainly not optimal (although<br>
subdirs might be acceptable in some cases). However,<br>
neither is writing in /usr/share :-)<br></blockquote><div><br></div><div>Ok, agreed on the last two points! :)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span style="color:rgb(80,0,80)">> Since the recommendation for mythweb is to run with SELinux off, I'm</span><br><div class="im">
> starting to like the idea of symbolic links to somewhere in /var or<br>
> /var/cache for writable stuff.<br>
<br>
</div>I believe the FHS suggests /var/cache/www/ or /var/cache/<app>/<br>
as a possible locations, but it also clearly states that anything<br>
under /var/cache/<whatever> must have the app support<br>
having the content disappear (usually because of running out<br>
of disk space, and the system admin deleting the caches),<br>
and I am have not reviewed the code to insure that mythweb<br>
will support a system admin deleting the files while it is running<br>
(one would have to test). In theory it should, but we do have </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
practice (which may be different).<br></blockquote><div><br></div><div>Yeah, I don't know what I was thinking before, I think /var/lib/mythweb is far more appropriate and in line with what mythtv does. I've got a test package for 0.26.1 that I'm going to test out on my combined FE/BE.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Note that apache must be configured to follow symlinks.<br>
The default conf only follows symlinks under the .../data/<br>
directory (not the base one). There are numerous<br>
potential solutions to that issue, of course.<br></blockquote><div><br></div><div>The two "extra" directories in the base dir were being created by the spec file I inherited. I grepped through the source and couldn't find anything that uses them so I think those are definitely superfluous so if everything is written under mythweb/data we should be OK.</div>
<div><br></div><div>Thanks,</div><div>Richard</div></div></div></div>