But if that loop ever stops running, the 'file' will block.
Ah, effectively a "replinishing" pipe. That would work. The downside, as you mentioned, is that it must be supported by a running process.
It would be nice to have a native file type (again, like an SQL view) that contains "instructions" to materialize data, but only materializes such data when it is read.
I am trying to add a permanent route on my server, but whenever i reboot it dissapears.
Please does anyone know the correct command to use.
route add XXX.XXX.XXX.XXX DDD.DDD.DDD.DDD
the above is what i have done.
ednut:)
using IRIX SGI software. (2 Replies)
On AIX 5.2 as root, installed Seamonkey and have to type
#/seakey/seamonkey/seamonkey to get it to run, which it does okay.
To set up a permanent alias, I did the following
(1) In a text editor
alias seamk='/seakey/seamonkey/seamonkey'
and saved it to /home/alias_file
(2) In a text editor... (7 Replies)
Hi guys,
I'm running Solars 8 on a V100 server at home for testing.
If I switch user to root and do:
# echo $PATH
This is the output:
/usr/sbin:/usr/bin
I'm using rsync over ssh and need to add /usr/local/bin and /user/local/sbin.
I do this by running the line:
#... (3 Replies)
I set my TERM variable to work with SMIT and everything works fine but when I logged out and log in again I have to set the variable again.
How can I set a permanent variable into the system so it will be as I wish even if a reboot is needed?
I set variables this way:
export VAR=value (7 Replies)
I have a file that reads File (X.txt)
Contents of record 1:
rdrDESTINATION_ADDRESS (String) "91 971502573813"
rdrDESTINATION_IMSI (String) "000000000000000"
rdrORIGINATING_ADDRESS (String) "d0 movies"
rdrORIGINATING_IMSI (String) "000000000000000"
rdrTRAFFIC_EVENT_TIME... (0 Replies)
I read this article as a way to do a non-permanent of something.
I saw 2 problems. The first that my rm is located at /bin/rm. I would assume I would change the location to /bin/rm. The second my rm is a executable file and not a text file. So will replacing my rm file with the shellscript... (3 Replies)
I try to understand the meaning of an inode. I wonder whether
an inode is unique (I'm pretty sure it is) and
whether it remains the same inode regardless of whatever happens to the file, dir or whatever?
I read somewhere that an inode stores info about the file, size... so changing the... (4 Replies)
See attached video for a demo on how to move back and forth from the desktop view to the mobile view.
Currently this only works for the home page, but I will work on some new PHP code in the future to make this work with the page we are currently on.
Edit: The issue with making every page ... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT LINUX
fifo
FIFO(7) Linux Programmer's Manual FIFO(7)NAME
fifo - first-in first-out special file, named pipe
DESCRIPTION
A FIFO special file (a named pipe) is similar to a pipe, except that it is accessed as part of the file system. It can be opened by multi-
ple processes for reading or writing. When processes are exchanging data via the FIFO, the kernel passes all data internally without writ-
ing it to the file system. Thus, the FIFO special file has no contents on the file system; the file system entry merely serves as a refer-
ence point so that processes can access the pipe using a name in the file system.
The kernel maintains exactly one pipe object for each FIFO special file that is opened by at least one process. The FIFO must be opened on
both ends (reading and writing) before data can be passed. Normally, opening the FIFO blocks until the other end is opened also.
A process can open a FIFO in nonblocking mode. In this case, opening for read only will succeed even if no-one has opened on the write
side yet, opening for write only will fail with ENXIO (no such device or address) unless the other end has already been opened.
Under Linux, opening a FIFO for read and write will succeed both in blocking and nonblocking mode. POSIX leaves this behavior undefined.
This can be used to open a FIFO for writing while there are no readers available. A process that uses both ends of the connection in order
to communicate with itself should be very careful to avoid deadlocks.
NOTES
When a process tries to write to a FIFO that is not opened for read on the other side, the process is sent a SIGPIPE signal.
FIFO special files can be created by mkfifo(3), and are indicated by ls -l with the file type 'p'.
SEE ALSO mkfifo(1), open(2), pipe(2), sigaction(2), signal(2), socketpair(2), mkfifo(3), pipe(7)COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-12-03 FIFO(7)