Wednesday, September 8, 2004, 4:22:54 PM, Mick wrote:
>> Why should it ping? automount does that for you, if the host is
>> not alive it will
>> unmount the mount point.
>> Then it will periodically check for the host availability and,
>> when alive, remount the
>> mount point for you.
>>
>> Should freevo double automount's job?
>>
> This is a valid point. I have no way of testing, as my automount shares are
> on the device I ssh from to my freevo box. So my automunts are always
> available when I am coding on my freevo box.
> Maybe someone else can test: from freevo host, ls -lah your automount dir
> when you know the share is not available. If there is no delay then it
> would be more cpu friendly if we just check if the dir exists before adding
> it to display.
> Thoughts?
> Mick
Autofs only mounts the dir when entered. ls -lah doesn't work in this
case. Freevo only mounts the dirs when entering the movie_menu and
when the timeout is set to 30 secs autofs umounts the directory's
again. But entering/selecting the entry in movie_menu which was
umounted after 30 secs, autofs quickly mounts the directory again. The
same thing happens when one manually cd to that autofs dir.
So automounts are not always available and autofs only mounts on
demand.
The hostname before the directory entry in local.conf.py makes sure if
the host in question is up and running, when it's down there is no
entry in movie_menu.
I'm clueless how this hostchecking is done but it must be in the code
Soenke Schwardt submitted. Personally i don't care it just works fine.
;-).
/Robert
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
