More > JRiver Media Center 22 for Linux
Library Server serves only the LIBRARY and not the media? [SOLVED]
JimH:
ls is a Linux command. Use it at a Linux prompt.
Zhillsguy:
I feel there is possibly a slight communication issue here, maybe I'm missing something.
If you want your Linux clients to access the network share at boot: for my Debian, Pi3, and Mint boxes I added a line similar to below to the /etc/fstab file in all 3 (identical line added to all 3):
//(server.ip.add or name)/sharename /home/username/Music cifs auto,user,credentials=/home/username/netlogin 0 0
Netlogin is a text file with sharing credentials if needed. Get one machine working and go from there.
For the Debian machine I had to add the smb and cifs-util packages; for the Pi3, I had to go into pi settings from main screen and select "Wait For Network At Boot"(?), for Mint it worked out of the box with the added line.
Of course, these will not be MC "clients" now, and will need to do their respective importing, etc. like any other stand-alone pc, and suggest using one (win or Linux) machine as "master" for tagging, etc. All others access pre-tagged and processed files.
Hope this helps.
blgentry:
--- Quote from: pepar on June 15, 2017, 08:44:17 am ---My media storage is separate from my MC server. I'd prefer clients reading directly from the file server and not via the Library Server device.
--- End quote ---
What benefit does that have?
Brian.
pepar:
Personally, I have worked out the automounting of shares at login. That how my DebianXFCE/i3 NUC MC Library Server is configured. (My media is stored on an unRAID server.) When I set up my first client, also Debian/XFCE/i3 NUC, I installed MC and poked around the settings and selected the Library served by the first box. It will play content.
My question was if the played content was being read directly from the unRAID or via the NUC running MC Library Server. And that's where I am at this point.
Jeff
--- Quote from: Zhillsguy on June 15, 2017, 09:41:58 am ---I feel there is possibly a slight communication issue here, maybe I'm missing something.
If you want your Linux clients to access the network share at boot: for my Debian, Pi3, and Mint boxes I added a line similar to below to the /etc/fstab file in all 3 (identical line added to all 3):
//(server.ip.add or name)/sharename /home/username/Music cifs auto,user,credentials=/home/username/netlogin 0 0
Netlogin is a text file with sharing credentials if needed. Get one machine working and go from there.
For the Debian machine I had to add the smb and cifs-util packages; for the Pi3, I had to go into pi settings from main screen and select "Wait For Network At Boot"(?), for Mint it worked out of the box with the added line.
Of course, these will not be MC "clients" now, and will need to do their respective importing, etc. like any other stand-alone pc, and suggest using one (win or Linux) machine as "master" for tagging, etc. All others access pre-tagged and processed files.
Hope this helps.
--- End quote ---
pepar:
--- Quote from: blgentry on June 15, 2017, 10:08:23 am ---What benefit does that have?
Brian.
--- End quote ---
I try to outfit my "devices" CPU-wise based on the work that they are handling. There are many low power options, which is something I gravitate to. Some of my devices are fabless. So, At least, I am curious as to what is happening on each device.
Jeff
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version