Re: Linux, the final decision

From: Ed Murphy (emurphy42_at_socal.rr.com)
Date: 02/01/04 

Date: Sun, 01 Feb 2004 05:46:31 GMT

On Sun, 01 Feb 2004 01:00:14 +0000, The Ghost In The Machine wrote:

>>> It is possible to NFS mount a nonexistent machine. More precisely,
>>> the machine exists at the time of the mount but then goes down;
>>> the NFS mount then simply sits there, anticipating a restart
>>> of the down machine. Access attempts to files on that mount result
>>> in process hangs if one uses a hardmount; the idea at the time
>>> of the design was that the machine would eventually come back.
>>>
>>> Or one can NFS mount a machine, then the mounted machine decides
>>> to change its IP address by not renewing a DHCP lease or by being
>>> reconfigured.

> As you might have noticed, there are (at least) two general
> possibilities for design that are possible.
>
> [1] The system pretends the crash didn't happen and waits for
> the remote box to restart, then continues where it left off.
>
> [2] The system notifies the app that something went wrong, which
> the app then decides to notify the user, confusing him
> to some extent, then the app terminates.
>
> With NFS, one can get either option. :-) (I'd have to look to see
> how Windows deals with an analogous situation. One advantage
> of course is that Windows drivers have access to the GUI, which
> might be of some assistance for notification if a remote node
> decides to go down.)

I don't think I've ever tried NFS on Windows. In general, though,
Windows' response to an unavailable network share is to keep trying
for a while and then give up with a failure notification, i.e. your
[2]. Why NFS (or any other networking system) would do [1] baffles
me; if a specific app *wants* to wait forever, then it can simply
try again when the failure notification is received, right?

Relevant Pages

  • Re: Linux, the final decision
    ... >> possibilities for design that are possible. ... >> the remote box to restart, then continues where it left off. ... >> how Windows deals with an analogous situation. ... > for a while and then give up with a failure notification, ...
    (comp.os.linux.misc)
  • Re: Running a single app on a RDP connection
    ... provides remote applications without the rest of the desktop. ... is included out of the box in Windows Server 2008 Terminal Services. ... create an RPD icon that automatically loads the app. ...
    (microsoft.public.windows.terminal_services)
  • Re: run a dll as an app
    ... You might want to see if the updated Remote Wonder software fixes your ... Jason Tsang - Microsoft MVP ... >>Windows isn't rocket science! ... Error signature is App Name rundll32.exe. ...
    (microsoft.public.windowsxp.general)
  • RE: Cannot open Service Control Manager on computer...
    ... I'm having the same problem but ONLY on Windows 2000 machines. ... On Windows 2000 the app ... > ....to interact with a remote machine's service would be quite common. ...
    (microsoft.public.dotnet.distributed_apps)
  • I need a component for REMOTE PC Control
    ... I search one component, app, solution, ... ... "seemed" to Windows xP remote ... Prev by Date: ...
    (borland.public.delphi.thirdpartytools.general)