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 V7
pipe
PIPE(2) System Calls Manual PIPE(2)NAME
pipe - create an interprocess channel
SYNOPSIS
pipe(fildes)
int fildes[2];
DESCRIPTION
The pipe system call creates an I/O mechanism called a pipe. The file descriptors returned can be used in read and write operations. When
the pipe is written using the descriptor fildes[1] up to 4096 bytes of data are buffered before the writing process is suspended. A read
using the descriptor fildes[0] will pick up the data. Writes with a count of 4096 bytes or less are atomic; no other process can inter-
sperse data.
It is assumed that after the pipe has been set up, two (or more) cooperating processes (created by subsequent fork calls) will pass data
through the pipe with read and write calls.
The Shell has a syntax to set up a linear array of processes connected by pipes.
Read calls on an empty pipe (no buffered data) with only one end (all write file descriptors closed) returns an end-of-file.
SEE ALSO sh(1), read(2), write(2), fork(2)DIAGNOSTICS
The function value zero is returned if the pipe was created; -1 if too many files are already open. A signal is generated if a write on a
pipe with only one end is attempted.
BUGS
Should more than 4096 bytes be necessary in any pipe among a loop of processes, deadlock will occur.
ASSEMBLER
(pipe = 42.)
sys pipe
(read file descriptor in r0)
(write file descriptor in r1)
PIPE(2)