I think it is much more easy to get NFS working right... ;)
Just my 2 cents.
On Tue, 2 Aug 2005, Michael Crute wrote:
Well if you are a perl or python kinda guy you could write a more
sophisticated script to copy the files and update the database so that
everything is transparent as far as myth is concerned.
-Mike
On 8/2/05, Mark Knecht <[EMAIL PROTECTED]> wrote:
Mike,
Thanks for the idea. I like the idea of being able to record
locally for 15 hours safely and then just using the new NFS storage
for playback only, but I think it won't work from a practical
standpoint:
1) MythTV runs in conjunction with MySQL which is managing the data
files. If I simply move the data files to some other location then
MySQL won't know where they are for playback.
2) As far as I know MythTV expects all the data file to be in a single
location for playback. I've never heard of anyone having multiple
disks for playback, but if they could then your idea would possibly
work.
I like the idea though and will do some research to see if there's
a practical solution. Possibly some sort of logical disk drive? That's
a bit beyond my meager skill set.
Thanks,
Mark
On 8/2/05, Michael Crute <[EMAIL PROTECTED]> wrote:
Mark,
Here is my suggestion to get the best of both worlds (note my limited
knowledge of mythtv). Setup a shell script to copy all your video files
from
the myth capture directory over to the nfs share and delete the files
thus
clearing your local space and also allowing you to capture 135 hours.
You
could even cron it so you don't have to think about it. Pardon me if
this is
a gross misunderstanding of mythtv but if its not it should work like a
charm.
-Mike
On 8/2/05, Mark Knecht <[EMAIL PROTECTED]> wrote:
On 8/2/05, Matthew Cline <[EMAIL PROTECTED]> wrote:
On 8/2/05, Mark Knecht <[EMAIL PROTECTED]> wrote:
but how do I know it's being used? And how do I know that the
rsize
option is being used?
Thanks,
Mark
Could you watch the traffic between the two using something like
ethereal? This should tell you which protocol is being used.
Hi Matt,
OK, ethereal was pretty easy to use, and it does indeed show that
I'm using TCP for packat transfer. I see a proto=NFS packet followed
by a number of TCP packets with sizes of 8K bytes so this seems to
verify that both options I was looking for ar indeed working.
Thanks!
Unfortunately this means I'm no closer to the root cause of my real
problem which is mythbackend shutting down without warning. It
happened again just a few minutes ago. This all started happening
after I brought this NFS mount on-line as storage for the mythbackend
server. I suppose I'll have to go back to the reduced storage option
(15 hours instead of 120 hours) and make sure that it's really this
disk/PC/network connection.
Thanks again for your help.
Cheers,
Mark
--
gentoo-user@gentoo.org mailing list
--
________________________________
Michael E. Crute
Software Developer
SoftGroup Development Corporation
"In a world without walls and fences, who needs windows and gates?"
--
gentoo-user@gentoo.org mailing list
--
Bryan Whitehead
Email:[EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list
