1 |
Hope so! Thanks. |
2 |
|
3 |
On 8/2/05, Bryan Whitehead <driver@×××××××××.net> wrote: |
4 |
> I think it is much more easy to get NFS working right... ;) |
5 |
> |
6 |
> Just my 2 cents. |
7 |
> |
8 |
> On Tue, 2 Aug 2005, Michael Crute wrote: |
9 |
> |
10 |
> > Well if you are a perl or python kinda guy you could write a more |
11 |
> > sophisticated script to copy the files and update the database so that |
12 |
> > everything is transparent as far as myth is concerned. |
13 |
> > |
14 |
> > -Mike |
15 |
> > |
16 |
> > On 8/2/05, Mark Knecht <markknecht@×××××.com> wrote: |
17 |
> >> |
18 |
> >> Mike, |
19 |
> >> Thanks for the idea. I like the idea of being able to record |
20 |
> >> locally for 15 hours safely and then just using the new NFS storage |
21 |
> >> for playback only, but I think it won't work from a practical |
22 |
> >> standpoint: |
23 |
> >> |
24 |
> >> 1) MythTV runs in conjunction with MySQL which is managing the data |
25 |
> >> files. If I simply move the data files to some other location then |
26 |
> >> MySQL won't know where they are for playback. |
27 |
> >> |
28 |
> >> 2) As far as I know MythTV expects all the data file to be in a single |
29 |
> >> location for playback. I've never heard of anyone having multiple |
30 |
> >> disks for playback, but if they could then your idea would possibly |
31 |
> >> work. |
32 |
> >> |
33 |
> >> I like the idea though and will do some research to see if there's |
34 |
> >> a practical solution. Possibly some sort of logical disk drive? That's |
35 |
> >> a bit beyond my meager skill set. |
36 |
> >> |
37 |
> >> Thanks, |
38 |
> >> Mark |
39 |
> >> |
40 |
> >> On 8/2/05, Michael Crute <mcrute@×××××.com> wrote: |
41 |
> >>> Mark, |
42 |
> >>> |
43 |
> >>> Here is my suggestion to get the best of both worlds (note my limited |
44 |
> >>> knowledge of mythtv). Setup a shell script to copy all your video files |
45 |
> >> from |
46 |
> >>> the myth capture directory over to the nfs share and delete the files |
47 |
> >> thus |
48 |
> >>> clearing your local space and also allowing you to capture 135 hours. |
49 |
> >> You |
50 |
> >>> could even cron it so you don't have to think about it. Pardon me if |
51 |
> >> this is |
52 |
> >>> a gross misunderstanding of mythtv but if its not it should work like a |
53 |
> >>> charm. |
54 |
> >>> |
55 |
> >>> -Mike |
56 |
> >>> |
57 |
> >>> |
58 |
> >>> On 8/2/05, Mark Knecht <markknecht@×××××.com> wrote: |
59 |
> >>>> |
60 |
> >>>> On 8/2/05, Matthew Cline <matthew.cline@×××××.com> wrote: |
61 |
> >>>>> On 8/2/05, Mark Knecht <markknecht@×××××.com> wrote: |
62 |
> >>>>>> |
63 |
> >>>>>> but how do I know it's being used? And how do I know that the |
64 |
> >> rsize |
65 |
> >>>>>> option is being used? |
66 |
> >>>>>> |
67 |
> >>>>>> Thanks, |
68 |
> >>>>>> Mark |
69 |
> >>>>> |
70 |
> >>>>> Could you watch the traffic between the two using something like |
71 |
> >>>>> ethereal? This should tell you which protocol is being used. |
72 |
> >>>>> |
73 |
> >>>> |
74 |
> >>>> Hi Matt, |
75 |
> >>>> OK, ethereal was pretty easy to use, and it does indeed show that |
76 |
> >>>> I'm using TCP for packat transfer. I see a proto=NFS packet followed |
77 |
> >>>> by a number of TCP packets with sizes of 8K bytes so this seems to |
78 |
> >>>> verify that both options I was looking for ar indeed working. |
79 |
> >>>> |
80 |
> >>>> Thanks! |
81 |
> >>>> |
82 |
> >>>> Unfortunately this means I'm no closer to the root cause of my real |
83 |
> >>>> problem which is mythbackend shutting down without warning. It |
84 |
> >>>> happened again just a few minutes ago. This all started happening |
85 |
> >>>> after I brought this NFS mount on-line as storage for the mythbackend |
86 |
> >>>> server. I suppose I'll have to go back to the reduced storage option |
87 |
> >>>> (15 hours instead of 120 hours) and make sure that it's really this |
88 |
> >>>> disk/PC/network connection. |
89 |
> >>>> |
90 |
> >>>> Thanks again for your help. |
91 |
> >>>> |
92 |
> >>>> Cheers, |
93 |
> >>>> Mark |
94 |
> >>>> |
95 |
> >>>> -- |
96 |
> >>>> gentoo-user@g.o mailing list |
97 |
> >>>> |
98 |
> >>>> |
99 |
> >>> |
100 |
> >>> |
101 |
> >>> |
102 |
> >>> -- |
103 |
> >>> ________________________________ |
104 |
> >>> |
105 |
> >>> Michael E. Crute |
106 |
> >>> Software Developer |
107 |
> >>> SoftGroup Development Corporation |
108 |
> >>> |
109 |
> >>> "In a world without walls and fences, who needs windows and gates?" |
110 |
> >> |
111 |
> >> -- |
112 |
> >> gentoo-user@g.o mailing list |
113 |
> >> |
114 |
> >> |
115 |
> > |
116 |
> > |
117 |
> > |
118 |
> |
119 |
> -- |
120 |
> Bryan Whitehead |
121 |
> Email:driver@×××××××××.net |
122 |
> -- |
123 |
> gentoo-user@g.o mailing list |
124 |
> |
125 |
> |
126 |
|
127 |
-- |
128 |
gentoo-user@g.o mailing list |