From: Dhruv Matani <dhruvbird@gmail.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Arvind Kalyan <base16@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: NFS and fifos.
Date: Sat, 16 Jul 2005 23:25:01 +0530 [thread overview]
Message-ID: <3a9148b905071610559f494a3@mail.gmail.com> (raw)
In-Reply-To: <9a87484905071608565d4b2ec1@mail.gmail.com>
On 7/16/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 7/16/05, Dhruv Matani <dhruvbird@gmail.com> wrote:
> > On 7/16/05, Arvind Kalyan <base16@gmail.com> wrote:
> > > On 7/16/05, Dhruv Matani <dhruvbird@gmail.com> wrote:
> > > > Hello,
> > > > I can't seem to be able to use fifos on an NFS mount. Is there any
> > > > reason why this is disallowed, or is this is a bug? v.2.4.20.
> > >
> > > Are both the processes (reader/writer) on the same machine? FIFOs are
> > > local objects.
> >
> > Yes, but I'm accessing them through my remote[public] IP address.
> > The idea behind it is to have a fifo that works across the network
> > through an NFS mount. Is that possible?
> >
> > I serched google for 'socket file', and all that I got was 'fifo', but
> > they are to be used only on a singl machine for communication between
> > 2 or more applications, but couldn't find any file abstraction for
> > communication for processes on distinct machines. Do you know of any
> > such thing, cause I couldn't find any.
> >
>
> sockets.
Are sockets named files?
>
> --
> Jesper Juhl <jesper.juhl@gmail.com>
> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
> Plain text mails only, please http://www.expita.com/nomime.html
>
--
-Dhruv Matani.
http://www.geocities.com/dhruvbird/
The race of quality has no finish line.
~Anon.
next prev parent reply other threads:[~2005-07-16 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 10:44 NFS and fifos Dhruv Matani
2005-07-16 14:32 ` Arvind Kalyan
2005-07-16 15:49 ` Dhruv Matani
2005-07-16 15:56 ` Jesper Juhl
2005-07-16 17:55 ` Dhruv Matani [this message]
2005-07-16 17:57 ` Willy Tarreau
2005-07-16 20:47 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a9148b905071610559f494a3@mail.gmail.com \
--to=dhruvbird@gmail.com \
--cc=base16@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.