At 10:42 PM 1/1/2010, Roger Heflin wrote:

>And that should be a small enough number of recording to not cause issues.
>
>How long is it typically up before this sort of behavior happens?

Typically about 20 minutes. Not always, but typically (as I see it on 
30 mintue shows)

>The memory usage is dependent on title and description length, I 
>have ran into a situation where one of the titles/descriptions were 
>somehow messed up, and that cause some instability with mvpmc, and 
>if one of the titles were extra long that would cause memory usage.
>
>if you can duplicate it consistently try leaving a telnet window 
>into the mvpmc running and every so often and when it happens run ps 
>and see how much memory the mvpmc (and other) processes are using, 
>the mvpmc only has 12mb of ram so anything using too much (if I 
>remember right somewhere around 11mb of total usage gets messy ).

Will do.  I'm hoping that changing it over to using -r (a CIFS share 
instead of using mythtv protocol) will make the problem go away, 
which in and of itself say something


Here's the current output (when it's not erroring).
# ps
   PID  Uid     VmSize Stat Command
     1 root        244 S   init
     2 root            SW  [keventd]
     3 root            SWN [ksoftirqd_CPU0]
     4 root            SW  [kswapd]
     5 root            SW  [bdflush]
     6 root            SW  [kupdated]
     7 root            Z   [cifsoplockd]
     8 root            SW  [mtdblockd]
    66 root        240 S   /usr/sbin/telnetd
    97 root        216 S   udhcpc -i eth0 -n
   113 root            SW  [cifsd]
   116 root            SW  [cifsd]
   125 root        476 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   142 root        232 S   /bin/ntpclient -d -l -h 192.168.2.36
   145 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   146 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   147 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   148 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   149 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   150 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   151 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   152 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   153 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   154 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   155 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   156 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   157 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   158 root       8452 S   mvpmc -S 300 -F /Avarice/settings/setting.192.168.2.
   159 root        412 S   -sh
   163 root        344 R   ps
#





------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to