Jump to content

scottc

Members
  • Posts

    284
  • Joined

  • Last visited

Posts posted by scottc

  1. you need to change your mount points in the docker

     

    the easiest thing would be change your media mount points to a since one, something like /Media -> /mnt/user/

     

    then inside plex when your setting up your media directories you would do something like 

    /Media/Workout

    /Media/TV Shows

    etc..

     

    Make sure you have enabled user share in settings -> global share settings

  2. If you check out "Vanilla" forums, they are pretty fantastic. When Plex moved their forums over to Vanilla I was very happy. So simple to use,

     

    Not sure if I like the narrow format of the plex forum, seems like a lot of wasted space, spreading things out too much.

     

    Also as much as there is a definite increase in loading with avatars off there is still something going on because if I click on say the v6 forum it still takes awhile for all messages to load. I will get 1 or 2 then wait 15-30 seconds before the rest will show. This happens more Mornings and Evenings when the forums seem to be the busiest. A month or so ago this was not an issue.

     

    Personally i cant stand the plex forums now.  I use to be pretty active there but i rarely event go there since they changed to the new forum software

  3. seems to be the /var/log/sa folder that contains lots of files and it look like it use 122Mb on the 128Mb total...

     

    But I don't know why, and what to do to find out why and to prevent it!

     

    Look inside the /var/log/sa folder and see what files are in there. 

     

    Those files are system activities from the dynamix system stats/activities addon.

    If you're going to run that you need at least 384 meg log filesystem.

     

    Theres posts and threads in the forums here that gives instructions on how to make it larger. Typically this is handled in modifying your go file.

     

    I use the system stats addon and have increased my /var/log to 256m in the go file and i am only using 10%

  4. For me it only does it on the first container update.  on the next updates it works fine.  So if i have 3 dockers that need to be updated,  the first one will show the blank screen until finished, but the second and third ones will display everything as expected.

     

    This is the exact same behavior I see.

     

    Same here. This was not present in 6.1.2

     

    6.1.2 worked fine for me also.  This is something new in 6.1.3

×
×
  • Create New...