[mythtv-commits] Ticket #3802: autoexpire list does not show host, not good on multiple backends where recording reside in different locations.
MythTV
mythtv at cvs.mythtv.org
Fri Sep 28 02:31:08 UTC 2007
#3802: autoexpire list does not show host, not good on multiple backends where
recording reside in different locations.
-----------------------------------------------------------+----------------
Reporter: Chuck Peters <chuck.peters+mythbug at gmail.com> | Owner: cpinkham
Type: defect | Status: closed
Priority: major | Milestone: unknown
Component: mythtv | Version: 0.20-fixes
Severity: medium | Resolution: fixed
Mlocked: 0 |
-----------------------------------------------------------+----------------
Changes (by cpinkham):
* status: new => closed
* resolution: => fixed
Comment:
(In [14547]) Allow mythbackend's --printexpire command line option to take
an optional
hostname as an argument. If a hostname is given, only expirable
recordings
that were made on that particular backend are listed.
I don't see a whole lot of reason to show this information in any other
place
because the hostname by itself isn't all that valuable in large Myth
installations that utilize multiple storage directories or share the same
directories between multiple hosts. It only took a few minutes to
implement
this much though, so I decided to go ahead and do it.
Closes #3802.
This does not address the comment on the ticket about the Auto-Expirer
trying
to delete programs on non-connected backends. The current code does check
to
see if a backend is connected before it determines a file is expireable
and
tries to expire it. If this issue is reproduceable, please provide more
debugging information in a separate ticket as it is unrelated to this one.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/3802#comment:3>
MythTV <http://svn.mythtv.org/trac>
MythTV
More information about the mythtv-commits
mailing list