Hi All,
I use ioctl(fd,I_PEEK,&peekstr) call where
fd - fifo file descriptor,
peekstr - strpeek structure.
I was trying various settings for peekstr
fields but results are the same - EINVAL error.
What I do wrong?
Thank you,
Alexei
I use ioctl(fd,I_PEEK,&peekstr) call where
fd - fifo file descriptor,
peekstr - strpeek structure.
I was trying various settings for peekstr
fields but results are the same - EINVAL error.
What I do wrong?
Thank you,
Alexei
As far as I know this feature just isn't available in LinuxQuote:>Hi All,
>I use ioctl(fd,I_PEEK,&peekstr) call where
>fd - fifo file descriptor,
>peekstr - strpeek structure.
>I was trying various settings for peekstr
>fields but results are the same - EINVAL error.
Cheers
Michael
Named pipe is not available in linux. Recently I've implemented some
interprocess process with named pipes on win32, and found partial
replacement for it on linux - unix domain sockets.
--
Best regards,
Andrey Koubychev
>Named pipe is not available in linux. Recently I've implemented some
>interprocess process with named pipes on win32, and found partial
>replacement for it on linux - unix domain sockets.
Cheers
Michael
>Named pipe is not available in linux.
One frequently finds that Windows takes Unix concepts and mucks them upQuote:>Recently I've implemented some interprocess process with named pipes
>on win32, and found partial replacement for it on linux - unix domain
>sockets.
> >Hello Alexei,
> >Named pipe is not available in linux. Recently I've implemented some
> >interprocess process with named pipes on win32, and found partial
> >replacement for it on linux - unix domain sockets.
> Named pipes certainly are available on Linux... (See man 3 mkfifo)
Thanks again,
Alexei
Quote:> Cheers
> Michael
> > >Hello Alexei,
> > >Named pipe is not available in linux. Recently I've implemented some
> > >interprocess process with named pipes on win32, and found partial
> > >replacement for it on linux - unix domain sockets.
> > Named pipes certainly are available on Linux... (See man 3 mkfifo)
> Thank you all.
> I can create (mkfifo) named pipe and perform some open/close
> read/write operations on Linux.
> The goal of my question was - how can I determine any data available
> for reading?
> On Solaris (SPARC and/or Intel) I used ioctl function described in my
> 1st message but seems this call does not work on Linux.
--
Communications Research Centre / RNS Tel (613) 998-2845
3701 Carling Ave., Fax (613) 998-9648
Ottawa, Ontario
K2H 8S2
Canada
> Hi All,
> I use ioctl(fd,I_PEEK,&peekstr) call where
> fd - fifo file descriptor,
> peekstr - strpeek structure.
> I was trying various settings for peekstr
> fields but results are the same - EINVAL error.
> What I do wrong?
> Thank you,
> Alexei
DS
>> >Hello Alexei,
>> >Named pipe is not available in linux. Recently I've implemented some
>> >interprocess process with named pipes on win32, and found partial
>> >replacement for it on linux - unix domain sockets.
>> Named pipes certainly are available on Linux... (See man 3 mkfifo)
> Thank you all.
> I can create (mkfifo) named pipe and perform some open/close
> read/write operations on Linux.
> The goal of my question was - how can I determine any data available
> for reading?
--
System Developer, UtelSystems a/s
w w w . u t e l s y s t e m s . c o m
>This is, of course, patently false.
--
bringing you boring signatures for 17 years
>>>Named pipe is not available in linux.
>>This is, of course, patently false.
>what it is a terminology problem, as you noted later but didn't apply to
>this part of your response. the `named pipes' that win32 provides are
>sufficiently different from what linux (and unix) provides that one might
>as well consider them different things. there is no implementation ms'
>notion of named pipes for any other platform, of which i am aware.
1. Please Help - Linux:Having trouble using fifo (named pipes)
I'm trying to get two processes to communicate using a fifo. The
problem is that the processes have different UID and the one that makes
the call to mknod() doesn't grant write-permissions on the fifo to other
users, no mather how I set the permissions.
The call is like this:
mknod(FIFO_NAME, S_IFIFO|0666, 0);
For the other process to write to the fifo (which is my intention) I
have to do a chmod directly on the shell to alter the fifo's permission.
Could someone please tell me what I'm doing wrong or if there is
something that I should be doing that I don't know about?
Thank you.
+--------------------------------------------------+
| Miguel Eduardo Cardoso Ferreira da Costa |
+--------------------------------------------------+
| www: http://caravela.di.fc.ul.pt/~i21118 |
+--------------------------------------------------+
3. syslogd pipe to named fifo, how?
4. troubles with compiling kdelibs
6. 2.4.2-SMP: problem locking nfs files mounted on HPUX (ENOLCK)
7. IPC with FIFO's (named pipes)
8. Creating a wrapper for 'stat'
10. Shells and FIFO's (named pipes).
11. named pipes / select / fifo
12. named pipe (fifo) file size always zero