On Saturday 29 December 2007 20:05, Joe Harris wrote:
> I have a similar setup and have used netfs to mount the drives.  There is
> a little lag at first after the drive disconnect, but since freevo 1.7.3
> (or maybe a little before), if I go back to the main screen it will
> re-check the directories and only show what really exists.  If one of my
> back-end servers goes down and back up...all is well...if it stays down,
> those items remove from my movie list.  It looks to whatever existed in
> local_conf.py at freevo start time and removes what is not there.
>
> ex. of what is in my fstab:
>
> //nas4/1500raid-a       /video/1500raid-a       cifs
> nosuid,nodev,noexec,rw,uid=500,gid=500,file_mode=0664,dir_mode=0755,credent
>ials=/root/.cred 0 0
>
> and the file /root/.cred has:
>
> username=user
> password=pass

Hi,
I must confess that it took me a while to understand that "netfs" just 
implements the cifs file system for red hat boxes. (...while I am not really 
sure about that.)
IMHO, your solution means that the samba/cifs share is statically mounted, 
which just does not work as long as the server is down while the client is 
booting. I just wonder why the share should be mounted when the server boots 
up after the client. Have you tried this?
Regards,
        Thorsten


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to